-
Notifications
You must be signed in to change notification settings - Fork 2
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
Just not working #1
Comments
There was a breaking change in the plugin interface. Code is refactored to support both v4 and v5. I've only tested v5.5.3 here, but the refactor is heavily borrowed from https://github.com/mrmckeb/typescript-plugin-css-modules Closes await-ovo#1
Opened a PR that "works on my machine" (tm). Feel free to give it a try #2 Edit: I've pushed a compiled version to a tag, so you can try it in your package.json using |
I'm having what I think is the same problem - just spent several hours trying to figure out why it didn't work. It looks like this package hasn't been published since #2 merged? would greatly appreciate if you could publish a new version with TS 5 support. |
This is an amazing project and I could use this really badly.
The problem is, it is just not working. I checked everything: used the workspace version of TS in vscode, added the plugin declaration accordingly to
tsconfig.json
and even tried to inspect thetsserver.log
but found nothing unusual. The plugin seemed to have just started fine but I still get the "Cannot find module './example.yaml' or its corresponding type declarations." message.I want this plugin because I tried to get
yaml
support for typescript imports in a nextjs project. After many considerations a usedyaml-loader
to load the files and it works fine with the webpack config. I understand that a working bundler has nothing to do with the typescript interpreter and I found a link to this repo in eemeli/yaml-loader#29. It would be absolutely fantastic, if this package could even support the same config as the loader or come with the loader altogether, but that is not the current issue.The only difference in my case is a new typescript version. Currently I am using
5.5.3
. Is there any chance that this could be fixed? I noticed that there are hardly any projects that solve the issue of importingyaml
into typescript and I really want this functionality :)The text was updated successfully, but these errors were encountered: