-
Notifications
You must be signed in to change notification settings - Fork 27.4k
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
links are broken in dev mode in the with-zones example #14242
Comments
thanks for making nextjs guys! you're the best |
Timer
added
good first issue
Easy to fix issues, good for newcomers
examples
Issue was opened via the examples template.
labels
Jun 16, 2020
Timer
added
kind: story
and removed
good first issue
Easy to fix issues, good for newcomers
labels
Jun 16, 2020
@lfades , I can write a fix for this |
Closed
rokinsky
pushed a commit
to rokinsky/next.js
that referenced
this issue
Jul 11, 2020
[ch3480] Fixes vercel#14242 Closes vercel#14264 Updated the readme of the `with-zones` example to use `vercel dev` instead, starting the app independently has some routing issues that don't happen on production (due to `vercel.json`), with `vercel dev` the app will match the production deployment on localhost.
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug report
Describe the bug
if you straight up clone /examples/with-zones, 'yarn dev' doesn't work in the root directory, so you have to run
yarn dev
in each zone independently, and then the cross-zone links breakTo Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
yarn create next-app --example with-zones
yarn && yarn dev
failscd blog && yarn && yarn dev
cd path/to/$APPNAME/home && yarn && yarn dev
Expected behavior
I expected the 'with zones' example to work like other examples, in that i could just cd into it and run
yarn && yarn dev
and it would work locallySystem information
Additional context
Thought this could help solve my issue of global styles screwing up my 3d game but unfortunately the local development is a bit wonky. It probably works if deployed, but then we gotta deploy our app for each change locally, just to get cross-zone linking to work.
A much better solution for my use-case would be per-page global styles
The text was updated successfully, but these errors were encountered: