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

Hook tsconfig "extends" resolver to resolve "ts-node/node14/tsconfig.json" to self when globally installed #1239

Open
cspotcode opened this issue Feb 23, 2021 · 0 comments
Labels
research Needs design work, investigation, or prototyping. Implementation uncertain.
Milestone

Comments

@cspotcode
Copy link
Collaborator

cspotcode commented Feb 23, 2021

Follow-up to #1202

If running the globally-installed ts-node, and tsconfig "extends" points to a "ts-node/node*/tsconfig.json", and local resolution fails:
Fallback resolve to the globally-installed ts-node

Although, in these situations, tsc will fail to resolve. So is this really a good idea? Need to think about it.

@cspotcode cspotcode added the research Needs design work, investigation, or prototyping. Implementation uncertain. label Feb 27, 2021
@cspotcode cspotcode added this to the next milestone May 15, 2021
@cspotcode cspotcode modified the milestones: 10.2.0, next Aug 8, 2021
@cspotcode cspotcode modified the milestones: 10.5.0, next Feb 7, 2022
@cspotcode cspotcode modified the milestones: 10.6.0 or 10.5.1, next Feb 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
research Needs design work, investigation, or prototyping. Implementation uncertain.
Projects
None yet
Development

No branches or pull requests

1 participant