Birk Skyum
Explore posts from servers[Svelte + Vite + Deno 2.0] Svelte and Vite configuration without a package.json
Thank you for the repro - i see the same error
is it important for you to use deno.json for config, or would it be fine if I can make it work using the package.json with deno v2 instead? deno has a bit better node compat that way
8 replies
[h3] [unhandled] H3Error: Client-only API called on the server side. Run client-only code in onMount
23 replies
[error] Client-only API called on the server side. Run client-only code in onMount, or conditionally
The only solution I've found so far is to delete lockfile+node_modules and install again, with varying results depending on package manager. Do you have an explicit vite version set as well?
21 replies
Demo for Desktop App
I hope when Deno 2 lands, and the DENO_FUTURE=1 is baked in, that it'll be easier to assess the preliminary Tauri support that does exist at this point. Haven't tried using it much with deno yet though, but some pieces appear to work - https://github.com/denoland/deno/issues/20738
10 replies
SolidStart ver.1
There is a ticket here for most of these issues
https://github.com/vercel/nft/issues/421
15 replies
SolidStart ver.1
SolidStart builds on top of Vinxi which sits on top of Nitro/Vite which are maintained by other teams. The
nitropack
(Nitro) pulls in @vercel/nft
which is pulling in @mapbox/node-pre-gyp
which pulls in npmlog
etc, so not to come with excuses, but some of these issues likely better to resolve upstream by the Nitro, Vercel or Mapbox team.15 replies
deno w/ svelte kit
This PR will fix a few sveltekit related issues, so I'll help reassess the situation when it's in https://github.com/denoland/deno/pull/23634
9 replies