-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Destruction of TypeScript ecosystem on npm is expanding #32273
Comments
My proposal is #18588 (comment). You just implement it. |
I believe that the best option is to just use pnpm, which doesn’t have this problem, as packages are stored in isolated trees and are symlinked to each other. pnpm file hierarchy for
TypeScript only looks into |
@ExE-Boss, hello. I came to this ticket by the opposite reason. I'm already using pnpm actively in my non-TS projects. However, when I try to install
(I depend on |
Looks like my issue is #30858, but not sure. |
As I mentioned at #31148, unused @types files installed by node modules pollutes and breaks the main project. It is caused by del package at that time. Now this problem came to be spread by another major package npm-check-updates. This means the destruction of ecosystem is expanding. TypeScript must resolve the problem quickly. See a solution #18588 (comment).
The text was updated successfully, but these errors were encountered: