-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: switch to using package_json
for interacting with package.json
#466
Conversation
87d0b8f
to
994e8b0
Compare
d82c432
to
e507562
Compare
2e394b9
to
bf17a19
Compare
33dbc15
to
e252e48
Compare
Discussed this in our guild meeting today: we're going to land it as-is so that it's in the history, and immediately follow up with switching to using That's not to say we won't potentially explore and switch to another package manager in the future, but doing so would be in response to a wider choice rather than Rails specific, which is what this PR is meant to enable |
This allows us to support all of the major javascript package managers by relying on the
package_json
gem to handle running and generating commands for a particular package manager.Currently I'm making our template actually agnostic and have setup to test that is the case by running against the major package managers + Yarn PnP, though I expect after landing this we'll decide on a single package manager to use going forward and remove code that is needed for the other package managers.