Skip to content
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

[Chore] Rearrange remix dependencies #815

Merged
merged 1 commit into from
Apr 24, 2024
Merged

Conversation

paulomarg
Copy link
Contributor

@paulomarg paulomarg commented Apr 24, 2024

WHY are these changes introduced?

We accidentally made @remix-run/node a direct dependency of the remix package when we introduced the Vercel adapter. While every Vercel app already needs to have the node package, every non-node app won't need that package.

WHAT is this pull request doing?

Making the node dependency a dev + peer combo, which means it's installed locally for development and expected to be installed in the app (which it already is in the template, and will have to be to run on Vercel anyway).

Type of change

  • Patch: Bug (non-breaking change which fixes an issue)

Checklist

  • I have used yarn changeset to create a draft changelog entry (do NOT update the CHANGELOG.md files manually)

@paulomarg paulomarg requested a review from a team as a code owner April 24, 2024 13:24
@paulomarg paulomarg force-pushed the remove_remix_run_node_dep branch from d23a5d5 to 1b5d80e Compare April 24, 2024 13:59
@paulomarg paulomarg changed the title [Chore] Rearrange and update remix dependencies [Chore] Rearrange remix dependencies Apr 24, 2024
@paulomarg paulomarg merged commit 50a36c8 into main Apr 24, 2024
19 checks passed
@paulomarg paulomarg deleted the remove_remix_run_node_dep branch April 24, 2024 14:13
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