Gabriel Halle

Was missing a check to only add the import if it's actually needed, looks like that caused some issues.

I think the `serverResource` transform should probably be moved above the `renameServer` transform so that the server calls can all be renamed but doing so causes an error with the...

Should be ok to merge now.

Ended up finding an off by one error using something like this: ```typescript export function routeData() { server((a: number, b: number, c: number) => { console.log("handler0", a, b, c) })(1,...

Rebased this, also not quite sure why github displays the diff for `babel.js` like that, there isn't actually that much change, the vscode built-in diff view displays it correctly.

I can confirm this and also the same thing happens for api routes. Seems like this happens because links are handled by https://github.com/solidjs/solid-app-router while files inside the public folder and...

Ended up changing the code to instead forward all headers (except `Accept` let me know if you think of any other ones). This should allow us to access headers like...

@ChristofFritz You can use [optimizeDeps.exclude](https://vitejs.dev/config/dep-optimization-options.html#optimizedeps-exclude) to exclude any dependency that is incompatible with vite. I've also personally opted for the following convention: any dependencies under `dependencies` in `package.json` gets externalized....

@shuhei The workarround doesn't seem to work for me it fixed the "standalone only works with a single entry point", but it introduced a new one: ``` node_modules\gulp-browserify\node_modules\brows erify\node_modules\umd\index.js:8 .replace(/\{\{name\}\}/g,...

Seems like the fetcher is being re-executed on the client even though the key is the same. This only happens when `createRouteData` is used with a function as the key....