-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
🐛 "useNodejsImportProtocol": "off" Didn't work #235
Comments
The biome.js configuration doesn't seem to be working, is vscode-plugin.biome not using biome.js? |
The configuration file is And where do you put the configuration file? |
yes, my is biome.json |
Is your configuration at the root of your project? From the look of it, it isn't, that's why it doesn't work. |
biome.json in my project. I have multiple projects in my workspace |
We have limitations in multi-root workspace support, please check the doc: https://biomejs.dev/reference/vscode/#my-biomejson-file-is-ignored-in-a-multi-root-workspace |
Since v1.8 we support LSP workspaces. Docs are outdated. @wuchuguang can you create a reproduction? |
Sorry |
s
I'll try using the local LSP |
I believe the issue comes from the extension itself that can't correctly resolve the Biome binary from a workspace project. This is tracked in: #201 |
VS Code version
1.89.1
Extension version
v2024.5.251958
Biome version
1.8.0
Operating system
Description
my beiome.js code
"useNodejsImportProtocol": "off" Didn't work
Steps to reproduce
1、I configured setting.json as provided by the plugin
2、biome init biome.js config
3、change biome.js like up
Expected behavior
4、Now in my code, I can't use require('path').
5、 npx biome lint is ok.
Does this issue occur when using the CLI directly?
No
Logs
The text was updated successfully, but these errors were encountered: