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
NodeNext compatibility #20
Comments
Hi, thanks for the issue, but could you give me a minimal example to reproduce the error or is it the same of the linked issue ? |
Hei @smartiniOnGitHub , I opened that bug in Fastify but it's not related to this. The workaround works, however it's just a double typecast and it does not solve the issue per se. NOTE: for some reason the link above does not retain "NodeNext": you need to go into TSConfig and specify it: |
ok perfect I'll take a look during next days and tell you something ... |
Hi, now I better understand the problem; but I have a little TypeScript knowledge so I'll need some time for the fix. |
Sorry this is longer than expected ... anyway in the repo you can see that I started the work on it (bump next release that will be 4.3.0 and upgrading all dependencies to latest, to be sure that all will be good); I'll tell more soon. Bye |
Update: changes almost done and all seems to work; now I only have to let the linter handle the new code in the right way. |
@marcoreni Hi, PR with code changes opened, please take a look at changes; I tested in another sample project that uses TypeScript with NodeNext and all should be fine. If not tell me, otherwise in a few days I'll merge this and prepare for a next plugin release. Thanks. Bye |
Hei @smartiniOnGitHub , I did a quick&dirty check by replacing the |
Release 4.3.0 of the plugin with the fix just published. Bye |
When using this plugin with
moduleResolution: nodeNext
, we encounter the same error as fastify/fastify-cors#223 .The text was updated successfully, but these errors were encountered: