Difference between npm run start and node .output/server/index.mjs in production result

[Kisagi07]

I'm sorry if this is something so obvious or stupid to ask, but what is the difference in production result between npm run start and node .output/server/index.mjs. I would assume the npm run start start the app in vinxi container and node .output/server/index.mjs is not. I don't really know much about deployment

[tamish-max]

In production, npm run start is usually just a convenience wrapper around whatever command you put in package.json.

For example, if your scripts look like this:

{
  "scripts": {
    "start": "node .output/server/index.mjs"
  }
}

then these are effectively the same app:

npm run start
node .output/server/index.mjs

The small differences are mostly around npm itself:

• npm injects lifecycle env vars
• npm adds node_modules/.bin to PATH
• npm runs exactly the script you configured

So the important question is not “Vinxi container vs not”, but “what does my start script actually point to?”. If it points at .output/server/index.mjs, then the production result is basically the same process.

For deployment, I’d normally pick one clear entry point and keep it consistent everywhere. Many teams use npm run start in docs/PM2/systemd/Docker so the command stays stable even if the underlying file changes later.

[MILLERMARRU]

For the default Node preset (no custom server.preset in app.config.ts), there's effectively no difference. npm run start is a thin wrapper around exactly the command you're comparing it to. SolidStart's build produces a Vinxi/Nitro server bundle at .output/server/index.mjs, and Vinxi's own docs describe running that production output with plain node .output/server/index.mjs, that's the documented way to start it, not a special container.

Where it does matter is if you configure a non-default server.preset (vercel, netlify, cloudflare, an edge preset, etc.). Those presets change what gets emitted, some don't even produce a long-running Node server at .output/server/index.mjs at all (an edge preset emits a module built for that runtime instead). For non-default presets, Vinxi also has an experimental vinxi start --preset <name> command meant to run the correct production entry for whichever preset you picked, so npm start matters more on a real deployment target than it does on the default Node one.

Since you're on the default preset from what you described, running either command should produce identical behavior. If you're seeing an actual difference, that would be worth digging into as its own issue rather than expected default-preset behavior.

[birkskyum]

We're focusing our limited maintenance resources on SolidStart v2, which should be fairly easy to migrate Solid v1 apps to.

It removes vinxi entirely, including the vinxi cli , in favor of using just standard vite cli which is documented here:

• https://vite.dev/guide/cli