-
Notifications
You must be signed in to change notification settings - Fork 25
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
Weird issue when formating Next Page components #132
Comments
Thanks for the report, @SalahAdDin. Would you be willing to create a minimal reproduction repo that we can take a look at? |
I had this same issue, not sure if the exact same error as I didn't print the error message, but I started creating a minimal reproduction repo and did not have the error there. Seemingly, closing VS Code and reopening it fixed the issue. 🙈 |
I will check it as soon as possible. |
We were seeing the same issue, and (for us) this is caused by importing a typescript type with the same name as the default export Minimal reproduction (the
|
@yuma-brendan that is only valid typescript when I'd recommend enabling Unfortunately, there's nothing we can do on our end to address this. |
We have the default behaviour on the linter and the those options in No way to fix it, right? |
If you have that option set in tsconfig then the code shared would not compile. Can you share a minimal reproduction that shows your uissue? |
Your Environment
Describe the bug
When trying to format the
page.tsx
files on my NextJS 13 project (with the app routing page), it fails terribly.To Reproduce
page.tsx
on a subroute or update it.Expected behavior
As it happens when we formatted in other files, all import should be ordered without any fail.
Screenshots, code sample, etc
Configuration File (cat .prettierrc, prettier.config.js, .prettier.js)
Error log
Contribute to @ianvs/prettier-plugin-sort-imports
The text was updated successfully, but these errors were encountered: