Closed eps1lon closed 5 months ago
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
19-react-dev | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Jun 11, 2024 8:51pm |
react-dev | ✅ Ready (Inspect) | Visit Preview | Jun 11, 2024 8:51pm |
npm install react@rc
would add the latest RC with a caret range topackage.json
which is generally unsafe since any prerelease may contain breaking changes. Especially in our case where commit hashes are encoded in the prerelease version. The caret range might match a version that was release earlier due to alphanumeric ordering.npm install --save-exact react@rc
will not use the caret range. This is the default behavior of for PNPM so I'm less concerned with documenting install instructions. You're on the save side if you just prepend ap
to the NPM command.