-
Notifications
You must be signed in to change notification settings - Fork 22
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
Unexpected errors with NPM run build #62
Comments
Hi there @Vickysomtee , thanks for the report. This was probably introduced by the fix for #61 😮💨 These are edge-cases where typings are not being representative of the actual code behavior. I'll try and reproduce this error but would greatly appreciate if you could share a code example. |
Been making modifications to the tsconfig in order to force the error to happen on the import specs, using tsc, to no avail. Maybe this has to do with a specific version of Typescript used in the NestJS project, or a tsconfig enforced by NestJS. No way to know without an example we can use to reproduce the error. |
Hello, I have been also experiencing this issue with package (v5.2.0), here's the configuration to reproduce the issue: tsconfig.json
sample_code.ts
|
I'm still being unable to reproduce this with the example you've shared @Nabil-249 Could you share your package.json dependencies? I'm still wondering if it's a Typescript version issue. |
I've just reverted to Typescript v4.9.5 and was able to reproduce the behavior. I'm evaluating whether this should be prioritized given that the last v4 version of Typescript was released in January 2023 and there's been 20+ releases of v5 since then. Would definitely be easier if Microsoft was less vague about Release and Support (i.e. EOL) schedules: |
I'll be following on fastify's footsteps here:
Source: fastify/fastify#4873 (comment) Closing this issue. If you see the same error with the latest version of Typescript feel free to open a new issue and include a reproduction repo 👍🏼 |
If someone else faces this currently, I solved the same error by:
|
Yes, in my case i upgraded my typescript from 4.9.5 to the latest version (5.4.5) fixes the issue, thank you! :) |
Hiya.
We have been using this package on our nestjs application for while and everything has been working fine.
Lately we started getting these two errors in our docker
npm run build
process. We have upgraded to the latest version5.2.0
and switched between node versions but the error still persists.The text was updated successfully, but these errors were encountered: