Skip to content

feat: switch to using package_json for interacting with package.json#466

Merged
G-Rath merged 20 commits intomainfrom
use-package_json
Sep 6, 2024
Merged

feat: switch to using package_json for interacting with package.json#466
G-Rath merged 20 commits intomainfrom
use-package_json

Conversation

@G-Rath
Copy link
Copy Markdown
Contributor

@G-Rath G-Rath commented Aug 12, 2023

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.

@G-Rath G-Rath force-pushed the use-package_json branch 4 times, most recently from 87d0b8f to 994e8b0 Compare August 12, 2023 23:18
@G-Rath G-Rath force-pushed the use-package_json branch 15 times, most recently from d82c432 to e507562 Compare August 15, 2023 20:29
@G-Rath G-Rath force-pushed the use-package_json branch 9 times, most recently from 2e394b9 to bf17a19 Compare August 26, 2023 20:48
@G-Rath
Copy link
Copy Markdown
Contributor Author

G-Rath commented Jan 26, 2024

Bun tests are currently broken because of oven-sh/bun#8406 / oven-sh/bun#9135

@eoinkelly
Copy link
Copy Markdown
Contributor

I think we should be opinionated about which JS package manager we support. It's cool we can support many but for our own sanity, baking one into this repo makes sense to me.

@G-Rath
Copy link
Copy Markdown
Contributor Author

G-Rath commented Sep 6, 2024

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 npm as our preferred package manager as that aligns with what we use everywhere else currently.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants