-
Notifications
You must be signed in to change notification settings - Fork 18
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
Svelte 4 support #121
Comments
Hey, yes it is. I saw the v4 release and plan to have a look at what must be changed. If you just want to test and dont rely on jest, you should consider vitest, which proves to be very good with ESM format. |
Hi, glad to hear that. I just changed a bit here and there to make them work, nothing blocking on my side. So I don't see any value for me currently to switch to vitest, but thanks anyway on the tip, really appreciated.
|
Hey @sebastianrothe, any update here on svelte v4 support ? |
Sorry, I was busy with other projects. If someone can jump in with a PR, please go ahead. |
Just reading through https://svelte.dev/docs/v4-migration-guide#removal-of-cjs-related-output means it will be more difficult to support CJS. It needs to use a bundler like esbuild to convert the output to CJS. It also means that the codebase could be converted to ESM entirely. The old version will still support both formats if you use Svelte < 4. |
As of right now, you'll need to use ESM with Svelte 4. Though there's an issue about CJS support for Svelte 4: #166 To use ESM with Svelte 4:
I upgraded a random library I found, You may also consider migrating to vitest, which generally works much better in my experience and is the officially recommended unit testing solution. There's a tool to automatically migrate though I've not tried it myself |
Released as v3.0.0 https://www.npmjs.com/package/svelte-jester |
Hi, I'm wondering if this library is still maintained.
Svelte 4 has been released few days ago, and I needed to change how the tests were written, to be able to get them to work.
Is this something it's planned on your side?
Thanks
The text was updated successfully, but these errors were encountered: