Fatih Aygün

I think both [Imagetools](https://github.com/JonasKruckenberg/imagetools) and [Unpic](https://unpic.pics/img/) are more than adequate solutions for this. Closing.

This is a [problem with Vite](https://github.com/vitejs/vite/issues/3288). Currently it doesn't support breakpoints or sourcemaps on the server code. Here's my solution to this problem: https://github.com/cyco130/vavite/pull/17. It uses Node's experimental ESM loader...

@gsxdsm Now there's a solution: https://github.com/cyco130/vavite/pull/17 It may one day make it into Vite itself, maybe.

> but not having any luck [Here's an example repo](https://github.com/cyco130/svelte-kit-node-loader). Feel free to open an issue at vavite's repo or hit me on [Rakkas's Discord channel](https://rakkasjs.org/chat).

Thank you for reporting! This is [a bug in Node.js itself](https://github.com/nodejs/node/issues/47566) and, per the comments on the issue, will be fixed in 20.1.0 (or 20.0.1 if one is ever released)....

Reopening because 20.1.0 was released today but it hasn't solved the problem. I'm still pretty sure it's a Node issue but we need to investigate just in case.

I now know the root cause: Node 20 runs ESM loaders in a separate thread but Vavite's loader relies on a global variable. This will require a substantial rework of...

Thanks for reporting! I'm gonna have a look but I'm gonna have to assign a low priority since: - This seems to be a StackBlitz issue. It works fine on...

Thanks, not a bad idea at all!

This is an ESM only package now. But it's still possible to use it from CJS: You will have to use dynamic imports like this: ```ts const { walk }...