-
-
Notifications
You must be signed in to change notification settings - Fork 69
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
support native Node.js Typescript type-stripping #441
Comments
We should wait for #440 to be merged. |
I can take It @jean-michelet |
@jean-michelet I gave a look, but unfortunately I am not able to progress into this (missing knowledge on my side) |
Have you had a look at runtime module? I think we should detect the use here. But I haven't tested this new Node feature yet, I'll have a look. |
I gave a look to those links, but I cannot find a way in which the auto enable type stripping is checked, because it only looks for |
You can have access Node version on I think |
@mcollina So it does break the test that expect this error: https://github.com/fastify/fastify-autoload/tree/master/test/issues/369 For now, all I can think of is a wonky combination of a conditional test execution based on runtime Node version and ignoring coverage for L148. |
Should we offer a way to enforce |
No, I don't think we should enforce it to false. |
I would not try to check the cli option either. |
Closed by #442 |
Given that Node.js v23 has unflagged type stripping, I think we should support it out of the box
The text was updated successfully, but these errors were encountered: