We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://github.com/EvgeniyBudaev/base-docker-go-next/tree/main/web
Current behavior: eslint error Expected behavior: No eslint error
Operating System: Platform: linux Arch: x64 Version: #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 4 14:39:20 UTC 2 Available memory (MB): 31375 Available CPU cores: 16 Binaries: Node: 21.7.3 npm: 10.5.0 Yarn: N/A pnpm: N/A Relevant Packages: next: 14.2.3 // Latest available version is detected (14.2.3). eslint-config-next: 14.2.3 react: 18.3.1 react-dom: 18.3.1 typescript: 5.4.5 Next.js Config: output: N/A
Linting
next dev (local)
No response
The text was updated successfully, but these errors were encountered:
I am not facing it by the way. I think you must check your visual studio environment.
Sorry, something went wrong.
No branches or pull requests
Link to the code that reproduces this issue
https://github.com/EvgeniyBudaev/base-docker-go-next/tree/main/web
To Reproduce
Current vs. Expected behavior
Current behavior: eslint error
Expected behavior: No eslint error
Provide environment information
Operating System: Platform: linux Arch: x64 Version: #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 4 14:39:20 UTC 2 Available memory (MB): 31375 Available CPU cores: 16 Binaries: Node: 21.7.3 npm: 10.5.0 Yarn: N/A pnpm: N/A Relevant Packages: next: 14.2.3 // Latest available version is detected (14.2.3). eslint-config-next: 14.2.3 react: 18.3.1 react-dom: 18.3.1 typescript: 5.4.5 Next.js Config: output: N/A
Which area(s) are affected? (Select all that apply)
Linting
Which stage(s) are affected? (Select all that apply)
next dev (local)
Additional context
No response
The text was updated successfully, but these errors were encountered: