-
Notifications
You must be signed in to change notification settings - Fork 10
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
Module type declaration not found #21
Comments
Can you share your repo or reproduce it in stackblitz or codepen? |
It's just a local editor error message. |
Not sure if this is related, but subpath import requires If the config looks good, sometimes you'll have to restart the ts server to clear its error messages, in vscode. And if you are sure this is not a problem of this repo, would you close this issue? |
Other third-party subpath packages I've used have normal type hints, and I've tried to configure this to make the subpath package type hints work. |
Thanks for your input.
So I don't think setting the declaration files path is necessary, and setting If this error bothers you, please share me a reproducible repo so I can properly fix it. |
All projects that directly import the 'barcode-detector/pure' package will report this error. |
5.2.2 |
I've made a PR in your repo to solve this issue. It's because nuxt is using refs: |
Thank you very much, this was solved nicely by setting |
@Sec-ant do you know if there is a way to make this work with I have to use |
nevermind, this will not be an issue soon: |
@ollema Could you please provide a minimal setup so I can take a look? |
no need - this will be fixed in SvelteKit 2.0 |
just a heads up for any SvelteKit users that might stumble upon this thread - SvelteKit 2.0 was just released and now this package works great out of the box! |
When importing
barcode-detector/pure
orbarcode-detector/side-effects
ts warns that the module or its corresponding type declaration cannot be found.I'm not sure if this is because of my local ts environment or something else.
The text was updated successfully, but these errors were encountered: