Skip to content

Clarify using netlify dev when importing @netlify/next in docs #2081

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

Closed
sarahetter opened this issue May 2, 2023 · 5 comments
Closed

Clarify using netlify dev when importing @netlify/next in docs #2081

sarahetter opened this issue May 2, 2023 · 5 comments
Labels
v4 Issues related to the v4 Next.js runtime

Comments

@sarahetter
Copy link

Related: #2003

User is getting an error if they run next dev when using our advanced middleware - we should make it clear in the documentation for @netlify/next that you must run netlify dev and not next dev because of the edge function.

@MarcL
Copy link
Contributor

MarcL commented May 2, 2023

Should we move this to https://github.com/netlify/docs now @sarahetter?
We moved to the docs site as being the source of truth for the Next runtime.
Or should this be in the README?

@nickytonline
Copy link

I think the general advice should be always run netlify dev. Usually people run next dev to compare regular Next development mode and Netlify development mode if they run into issues.

@sarahetter
Copy link
Author

Should we move this to https://github.com/netlify/docs now @sarahetter? We moved to the docs site as being the source of truth for the Next runtime. Or should this be in the README?

This isn't for the runtime, it's for the next package - our advanced middleware

@MarcL
Copy link
Contributor

MarcL commented May 5, 2023

Ok - The docs for the next package also point to the docs site from the README.
It feels like that should still be the source of truth.

@MarcL MarcL added v4 Issues related to the v4 Next.js runtime and removed Ecosystem: Frameworks labels Mar 13, 2024
@serhalp
Copy link
Contributor

serhalp commented Jun 4, 2024

Superseded by v5. Please feel free to reopen if this is still valid.

@serhalp serhalp closed this as not planned Won't fix, can't repro, duplicate, stale Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v4 Issues related to the v4 Next.js runtime
Projects
None yet
Development

No branches or pull requests

4 participants