Move all npm packages to @rails scope

[javan]

Fixes #33083

actioncable   → @rails/actioncable
actiontext    → @rails/actiontext
activestorage → @rails/activestorage
rails-ujs     → @rails/ujs

TODO:

• Perform the “move” by publishing all packages manually*
  • https://www.npmjs.com/package/@rails/actiontext
  • https://www.npmjs.com/package/@rails/actioncable
  • https://www.npmjs.com/package/@rails/activestorage
  • https://www.npmjs.com/package/@rails/ujs
• Ensure core team members are owners of new npm packages
  • npm owner ls @rails/actiontext
  • npm owner ls @rails/actioncable
  • npm owner ls @rails/activestorage
  • npm owner ls @rails/ujs

*npm doesn’t have a built-in system for moving or renaming packages

[kaspth]

Cool! What happens when people next go to call yarn install and the packages have been renamed?

[javan]

What happens when people next go to call yarn install and the packages have been renamed?

The packages aren't being renamed, technically. They're being published as new packages with new names. So, existing applications will need to update their package.jsons to point to the new packages.

[connorshea]

@javan shouldn't this be mentioned in the CHANGELOG and/or Release Notes?

[javan]

@connorshea, yes thank you! Added here e3d4333.

[benreyn]

I just ran into this issue on a project where I couldn't figure out why I wasn't getting this fix and there was no version 6.0.0 for rails-ujs. Does npm provide any mechanism for communicating this better? Other than digging through the changelog, issues, and source code, there was no (obvious) indication of this change. At the very least should a post-install script log a message that says something to the effect of rails-ujs has been deprecated. Please use @rails/ujs instead (This would involve a version bump to the old package)