-
Notifications
You must be signed in to change notification settings - Fork 131
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
[🐛 Bug]: ESLint rule no-app-not-found-runtime is exported as no-app-not-found #530
Comments
Thanks a lot for raising this @mattiasw 😄 ah... yeah you're totally right! 😓
That's my bad, I think that the two lines above are the only places that need this changed, since you ticket that you'd like to help fixing this bug, please let me know if you want to apply the changes or if I should 🙂 (PS: updating this is technically a breaking change... but I think it could be added as a patch since the rule name is actually wrong (and the docs do indicate it with the correct name) 🤔) |
I can do it. I was also wondering if this would be considered a breaking change or not. But I'm with you, the documented API will not change, it will just start working. :-) |
next-on-pages environment related information
Description
The ESLint rule that is called
no-app-not-found-runtime
in the documentation is exported asno-app-not-found
.Reproduction
next-on-pages/no-app-not-found-runtime
is set.export const runtime = 'edge';
to thenot-found.tsx
page.No error. But if changing the name to
next-on-pages/no-app-not-found
it works.Pages Deployment Method
None
Pages Deployment ID
No response
Additional Information
I can make a PR if you tell me whether it's best to change the documentation or to change the export.
Would you like to help?
The text was updated successfully, but these errors were encountered: