-
Notifications
You must be signed in to change notification settings - Fork 273
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
Improve monorepo DX #2154
Improve monorepo DX #2154
Conversation
We detected some changes in |
Oxygen deployed a preview of your
Learn more about Hydrogen's GitHub integration. |
Validated for cases:
@frandiox There is one case that I found that didn't work or broken. When running an example, when making edits to the skeleton template, the example doesn't get the new diff on files that didn't get override in the example folder. We used to be able to just |
|
||
if (isHydrogenMonorepo) { | ||
// Force reoptimizing deps without printing the message | ||
await removeFile(joinPath(root, 'node_modules/.vite')); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we also remove the node_modules/.vite
that now also appears in the skeleton folder when running npm run dev:app
or npm run dev
within the skeleton folder?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's the one we are removing here. root
should point to the skeleton template when running it there or with npm run dev:app
🤔
The files came from
I've added an extra watcher to make this possible. Now changes in skeleton source files should reflect in the diff example without restarting the dev server. Diff example files still have higher priority so they won't be overwritten by skeleton files even if they change. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for checking again. I've removed that banner completely since it's actually not that useful and it might be confusing 👍 |
dist/browser-prod
instead ofdist/browser-dev
, which is what we use in local development.hydrogen-codegen
Print a message when modifying the CLI source to remind us to restart theh2 dev
process (we can't do this automatically without creating more problems).h2 generate xyz
uses the latest files.npm run dev
in the CLI to get files applied in diff examples.Any other thing that is not working properly in local dev?