Newest Typescript breaks stuff #10695
Replies: 2 comments 1 reply
-
Hi, I experienced a similiar issue as 'module' was set to 'NodeNext' by default when setting up a new Sveltekit library. When building the library I got this warning:
Additionally, when trying to use the library in an application, it fails with: 'ReferenceError: exports is not defined'. By removing the 'module' from the |
Beta Was this translation helpful? Give feedback.
-
I am having the opposite issue, where using
This puts the onus on library maintainers to add an "types" export, which extends the Node interface. How do more experienced typescript users feel about just changing to "node16" or "nodenext" and diverge from Svelte (and Typescript) recommendations? |
Beta Was this translation helpful? Give feedback.
-
Hello
I have discovered a problem that could affect people using SvelteKit in larger projects:
In a SvelteKit project with:
Then using the latest versions for everything is fine, except for typescript itself; Installing a version beyond 5.1.6 results in:
And setting "module": "NodeNext" in tsconfig.json introduces a host of other issues.
Anyone have experienced this or has thoughts, workarounds, etc.?
Beta Was this translation helpful? Give feedback.
All reactions