David Volquartz Lebech

If you have `bind:value={$form.someValue}` on your form field, then the form will still get updated when the field changes. Therefore, it *looks* like `handleChange` is not necessary. However, `handleChange` both...

See also this issue which describes the same thing: https://github.com/tjinauyeung/svelte-forms-lib/issues/159#issue-1163956097

It looks like the build partially failed for the `node` version which I assume is the latest. The test suite looks ok.

From @spheenik in https://github.com/sveltejs/kit/issues/6440#issuecomment-1236823838 > If you manually patch this file, and add the following directly above the above mentioned code > > ```js > import { createRequire } from...

@theetrain > What vite/esbuild config worked for you? In my case, we're still on sveltekit next.471 and adapter node next.87, i.e. before the introduction of esbuild for including dependencies.

@theetrain Quick note, your reproduction repository looks like it has some issues, for example you're trying to access `fetch` in page.server.js and layout.server.js from the server load event, but `fetch`...

**Edit**: I figured out why external dependencies were not being respected in the esbuild. I was importing firebase as `@firebase/auth` instead of `firebase/auth`, and I guess esbuild couldn't figure out...

@stefanosala @jeffmcaffer I've now tested the current suite with `ioredis` and there are 8 failing tests. It's possible it's something minor, but at least it's not just a matter of...

@cchyung @cudr thanks for the "tricks"/"hack". However, they did not work for me with Apollo version (3.5.5) and latest Sveltekit (1.0.0-next.201), but removing the `.js` in `.cjs.js` filenames did it...

@ItzaMi > What can I do about this? The solution is hinted at in the issue description above. Use `@apollo/client/core` rather than `@apollo/client` for the client import. E.g. see the...