"AsyncLocalStorage" is not exported by "__vite-browser-external"
Installed the rc1, moved my code over, fixed up the issues coming from the v.3 release,
npm run build
dies with ../node_modules/vinxi/runtime/http.js (70:9): "AsyncLocalStorage" is not exported by "__vite-browser-external", imported by "../node_modules/vinxi/runtime/http.js"
Any suggestions on how to fix it up? Using node v20.12.212 Replies
It suggests server code is being pulled into the client. If I remember correctly "use server" happened after v.3 so that's probably missing somewhere.
edit: "use server" was introduced with v0.4.0 last December.
okay thanks, that's a good place to start. I'm wrapping almost everything in a
<ClientOnly>
as it's basically a SPA, but will do some digging.Typical places would be actions; though sometimes it's a badly structured import (i.e. don't rely on treeshaking, especially in dev).
The traceback of the error should lead you to the offending code (which is ultimatlely responsible for pulling in the server code).
that's the ugly thing, the traceback doesn't have any of my code in it:
Dev works fine, it's only on build unfortunately.
This error has me scratching my head:
entry-client.tsx
runs mount
there is no default export; though it's in build so I'm probably missing something.GitHub
solid-start/packages/start/src/client/mount.ts at 7ff375563f74aff34...
SolidStart, the Solid app framework. Contribute to solidjs/solid-start development by creating an account on GitHub.
yeah, and those files are straight from the start rc1 install, I've not modified them.
Likely a stupid and superfluous question on my part; can you successfully build the "basic" template?
hehe, yeah, the start + unocss template installs and builds fine, which is the one I started with.
oooh, that "default" does log in the new install as well:
seems like a red herring...
The good news is that If I remove all my routes and leave a stub route, it builds, so I'm off to slowly start adding routes back 1 by 1
Yep, never noticed it before.
I was on vite v5.2.8 but after a
pnpm update
nothing mysteriously broke the build.
so I'm off to slowly start adding routes back 1 by 1Sounds like a plan
... and it was! Found a stray
createServerAction$
. Removed it, and it all compiles now š