Skip to content
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

LSP shows error for the process object even with the no-process-globals rule disabled #26578

Closed
dmint789 opened this issue Oct 27, 2024 · 1 comment · Fixed by #26603
Closed
Labels
bug Something isn't working correctly lsp related to the language server

Comments

@dmint789
Copy link

Version: Deno 2.0.3

It's annoying that Deno LSP always highlights the process object as a warning, even with the lint rule no-process-globals disabled. It wants me to do the node:process import, but I can't use that in a Next JS application.

Steps to reproduce:

  1. Get the reproducible example here (make sure you get the exact branch and commit that is linked)
  2. Open VS Code with Deno LSP enabled
  3. Open the ContestForm.tsx file and scroll to one of the lines with the process error
  4. It should say Cannot find name 'process'

The same also works in the command line by running deno check .

@marvinhagemeister marvinhagemeister added bug Something isn't working correctly lsp related to the language server lint Issues related to deno lint labels Oct 28, 2024
@dsherret dsherret removed the lint Issues related to deno lint label Oct 28, 2024
dsherret added a commit that referenced this issue Oct 28, 2024
bartlomieju pushed a commit that referenced this issue Oct 29, 2024
@dmint789
Copy link
Author

The issue still persists on Deno 2.1.4. Steps to reproduce:

  1. Clone this repo
  2. Open VS Code with Deno LSP enabled
  3. Open the ContestForm.tsx file and scroll down to line 462, which uses the process global
  4. It should say "Cannot find name 'process'"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working correctly lsp related to the language server
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants