-
Notifications
You must be signed in to change notification settings - Fork 4
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
Export for directives can't be resolved #10
Comments
Additional testing
works well, while
Does not. Is there som specific config needed in our project to make this work? |
Interesting. This seems to works correctly in Node/dvlp/esbuild, but not yet in TypeScript. The fix has been merged (microsoft/TypeScript#49644), but evidently not yet released. I guess the only option is to manually add each export |
Correction: TypeScript can't resolve aliases via |
same problem with
|
Thanks @pumano, I'll look into that too. |
We are experiencing an issue with using
@popeindustries/lit@1.0.4
as a "proxy" for exports from@popeindustries/lit-html
.gives the error
Checking the file
node_modules/@popeindustries/lit/directives/unsafe-html.js
it containsThis file path points to nothing in the package
@popeindustries/lit-html
on disc innode_modules
.@popeindustries/lit-html
hassrc
andvendor
directories (andsrc/vendor
) which containsdirectives
. The export map of@popeindustries/lit-html
listsdirectives
aswhich seem to point to the right place. So why can't the typescript compiler resolve this import? Using the import directly from
lit-html
gives the same error, while pointing directly to e.g. thevendor
directoryworks as intended. This leads me to think that our project can't read/understand the exports map correctly, but shouldn't node 18.9 and typescript 4.8.3 be able to do that? On closer inspection it seems that it might be the wildcard export map that isn't understood, because addition of e.g
Seems to work well.
node version: 18.9.0
typescript version: 4.8.3
The text was updated successfully, but these errors were encountered: