Boye Lillejord-Nygård

@dummdidumm Thanks! I don't think we should remove the whole object, since you can set things like custom npm registry and access there, that make sense to copy over to...

@futantan I'm not too familiar with how changeset work, but the way we do it is to add this to the `package.json` of all packages we use `svelte-kit package` on:...

@Tal500 You can just import paths, but then you'll not use the library the same way others use it when it's distributed. The monorepos I work with are usually one...

@Tal500 Thanks for the example, but the alias and resolution of packages is not the problem. The problem is that the `svelte-kit package` command copies settings over to the generated...

If anyone finds this issue and needs a quick fix, we've created a [vite plugin](https://github.com/omnysecurity/vite-plugin-wasm-esm) to use your WASM packages as regular ES modules that also supports SSR. Only supports...

We use wasm-pack generated modules with SSR using this vite plugin: https://github.com/omnysecurity/vite-plugin-wasm-esm. Works well for us, but you have to use `web` as target when building with wasm-pack.

@zahachtah That's because in `d3-selection@3` the global event is removed (v2 is used here). You just need to remove the import (`import {event as currentEvent} from 'd3-selection'`), and add `currentEvent`...