[Bug]: "<A ..." triggers `ERROR Client-only API called on the server side.` under `vinix build` but not `npm run build`

[jcalfee]

$ vinxi build && vinxi start
...
 ERROR  Client-only API called on the server side. Run client-only code in onMount, or conditionally run client-only component with <Show>.                                               6:56:47 PM

  at notSup (.output/server/node_modules/solid-js/web/dist/server.js:1141:9)
  at .output/server/chunks/runtime.mjs:8590:10
  at ModuleJob.run (node:internal/modules/esm/module_job:271:25)
  at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:578:26)
  at async Object.run (/home/james/.local/share/pnpm/global/5/.pnpm/vinxi@0.4.3_@types+node@22.4.1_ioredis@5.4.1_terser@5.31.6/node_modules/vinxi/bin/cli.mjs:278:7)
  at async runCommand (/home/james/.local/share/pnpm/global/5/.pnpm/citty@0.1.6/node_modules/citty/dist/index.mjs:316:16)
  at async runCommand (/home/james/.local/share/pnpm/global/5/.pnpm/citty@0.1.6/node_modules/citty/dist/index.mjs:307:11)
  at async runMain (/home/james/.local/share/pnpm/global/5/.pnpm/citty@0.1.6/node_modules/citty/dist/index.mjs:445:7) 

Expected behavior 🤔

vinxi build and vinxi start should work just like package.json:

"scripts": {
    "build": "vinxi build",
    "start": "vinxi start"
  },

OR log a warning or error..

Steps to reproduce 🕹

Steps:

1. https://docs.solidjs.com/solid-start/getting-started
2. Edit src/app.tsx and change <a href="/">Index</a> to <A href="/">Index</A>, add import
3. vinxi build && vinxi start # builds but crashes when it goes to start
4. npm run build && npm run start # everything works

Context 🔦

Get rid of an incredible difficult bug to find.

Your environment 🌎

Pop!_OS 22.04 LTS
node v22.14.0
@solidjs/start@1.1.3

Duplicates

• I have searched the existing issues

Latest version

• I have tested the latest version

Current behavior 😯

[brenelz]

Is there a reason don't use the npm run build && npm run start commands instead of the vinxi ones directly

[jcalfee]

I usually use npm run ... but I needed a variation in the command line that I was using (relying on history), and knew that the npm command was just as the starter project, not adding anything. I just randomly worked up a command to go directly to vinxi and, after a while started hitting a bug. I'm upgrading so I had many things commented out already; I ended up changing so much that there was nothing left, my project's startup was exactly like sold starter project except for extra packages in package.json. This was the very last thing that occurred to me to try. It was not my first guess for the cause of this error, it was the actually the last.

Then I did checked, and it was reproducible in a clone of the solid start project mentioned above.

[birkskyum]

I can build and start it just fine, following the instructions above

https://stackblitz.com/edit/github-28x64bqv?file=src%2Fapp.tsx

[jcalfee]

I tested locally with node v18 instead of v22 and I still have the error locally. This may not matter, but I have npm version 10.7.0 and stackblitz has npm 10.2.3.

Stackblitz has: ℹ Building Nitro Server (preset: node-server, compatibility date: 2024-11-25) but I do not see that in my output and I can't seem to find where to set this date (it did not create that same info line you have in stackblitz).

Other than that, I'm running in docker (that really should not matter either). I'm perplexed. We can close this if you want unless you can think of something.

[jcalfee]

Ah, this works on my side:

$ npx vinxi build && npx vinxi start

My path was picking up a different version of vinxi; v0.4.3 instead of v0.5.3.

[jcalfee]

I was using pnpm before I went be to npm. I think it is a little invasive for pnpm to put their global shared location first:

# pnpm
export PNPM_HOME="/home/james/.local/share/pnpm"
case ":$PATH:" in
  *":$PNPM_HOME:"*) ;;
  *) export PATH="$PNPM_HOME:$PATH" ;;
esac
# pnpm end

I'm still curious how a version change could cause a the generated code to miss reference the Client-only API exception. It could be a sign that something could be improved.