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

Why are paths with colons unresolvable? #154

Closed
NullVoxPopuli opened this issue Feb 25, 2024 · 2 comments
Closed

Why are paths with colons unresolvable? #154

NullVoxPopuli opened this issue Feb 25, 2024 · 2 comments

Comments

@NullVoxPopuli
Copy link

NullVoxPopuli commented Feb 25, 2024

here is my repro: https://stackblitz.com/edit/stackblitz-starters-d2rfdx?description=Starter%20project%20for%20Node.js,%20a%20JavaScript%20runtime%20built%20on%20Chrome%27s%20V8%20JavaScript%20engine&file=my-library%2Fpackage.json,.gitignore,my-library%2F.attw.json,package.json,my-library%2Fcolon%3Ahere.d.ts&file=consumer%2Findex.ts,my-library%2F.attw.json&title=node.new%20Starter

tl;dr:

I want to import package-name/sub-path:colon

but it seems not allowed? and I can't figure out why?
this could be a TS bug, too -- as far as I can tell, : works just fine at runtime.

I opened an issue here: microsoft/TypeScript#57529

@NullVoxPopuli
Copy link
Author

Gonna close this, because the answer is to declare ambient type declarations, rather than rely on package.json#exports

@andrewbranch
Copy link
Collaborator

Yep: #107

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants