Pablo Berganza

I'm having the same issue with some of my packages. [This one being a great example](https://bundlephobia.com/package/@felte/[email protected]) since it's just a bunch of utils. I'm using Rollup to bundle these packages...

Upon further inspection I think I found a solution to this. Removing the `"browser"` property from my package's `package.json`, or pointing it to the `esm` output makes Bundlephobia report the...

You don't need to use `setErrors` to handle server side errors. [You can use the `onError` callback on the configuration object.](https://felte.dev/docs/svelte/validation#server-errors)

This seems to happen because Vite is grabbing the transpiled client code instead of the untranspiled one. And since the server version of `solid-js/web` does not export `setAttribute` it fails....

I can't find anything that I might be doing different compared to other packages. Can you confirm if this happens with any other components? E.g. [solid-app-router](https://github.com/solidjs/solid-app-router) also uses `setAttribute` when...

Hey, @davedbase. I had not tried to do SSR with Solid, but I used [solid-ssr's examples as a template](https://github.com/solidjs/solid/tree/main/packages/solid-ssr) and I'm not getting this error. It makes me believe that...

@millette @davedbase I managed to reproduce the issue using Astro. Adding this to vite's config solved the issue locally for me: ```javascript ssr: { noExternal: ['@felte/reporter-solid'], }, ``` If this...

> P.S.: I found the as prop on ValidationMessage was required otherwise I get this error: While I did find some issues when using this in SSR ([added a note...

Thank you so much for your interest! This really means a lot! First regarding the first part of your question: The reason I haven't focused that much on the Constraint...

Let's actually keep this open until the PR gets merged. I quite like the approach of letting the issue close by itself when merging a related PR. Since this issue...