Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Tsserver never picks up a new file #61663

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

Open
ipb26 opened this issue May 6, 2025 · 1 comment
Open

Tsserver never picks up a new file #61663

ipb26 opened this issue May 6, 2025 · 1 comment
Labels
Needs More Info The issue still hasn't been fully clarified

Comments

@ipb26
Copy link

ipb26 commented May 6, 2025

πŸ”Ž Search Terms

"tsserver does not pick up new files"

πŸ•— Version & Regression Information

This has been an issue for as long as I can remember.

⏯ Playground Link

No response

πŸ’» Code

No response

πŸ™ Actual behavior

I have an issue where tsserver (using code-server ide) refuses to pick up a new file in a node_modules for the purpose of intellisense / automatic imports. It picks up every other file in the same project and even the same folder, they all work fine with intellisense and automatic imports, but it will not pick up this one new file. Looking through the logs there is a relevant line for every other file in this project, but not the one I want. Not a single result in 50000 lines of logs if I ctrl+f the file name.

Manually typing in the import statement does work - the file is definitely there and valid and the ide recognizes it and picks up the correct types if I put it in manually.

Also restarting tsserver makes no difference no matter how many times I do it.

πŸ™‚ Expected behavior

Tsserver should pick up everything in node_modules.

Additional information about the issue

I just don't even know how to begin to debug this.

@RyanCavanaugh RyanCavanaugh added the Needs More Info The issue still hasn't been fully clarified label May 6, 2025
@RyanCavanaugh
Copy link
Member

We need concrete repro steps to be able to investigate issues. While an overall description is useful, we need specific and repeatable information in order to act on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs More Info The issue still hasn't been fully clarified
Projects
None yet
Development

No branches or pull requests

2 participants