Document the new npm package names in the upgrade guide #37131
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
As I was upgrading a rails 5.2 app to 6.0, I had to manually rename all references to the old npm packages (in the
package.json
dependencies
and in my app'simport
statements) to the new package names under the@rails
scope, as outlined in #34905:I thought it would be helpful to specifically mention this in the upgrade guide, so that's what this PR does. (I didn't include the
actiontext → @rails/actiontext
rename in the upgrade guide sinceactiontext
didn't exist in rails 5.2.)