Remix v1.16.1 fail to start ESM app server with tsx watch on Windows

[onemen]

What version of Remix are you using?

1.16.1

Are all your remix dependencies & dev-dependencies using the same version?

• Yes

Steps to Reproduce

With this configuration on Windows Remix fails to start custom server

configuration:

• remix 1.16.1.
• serverModuleFormat: 'esm'.
• one or more ESM dependencies.
• starting custom app server with tsx watch remix dev -c "tsx watch ./server.js"

You can reproduce this issue by installing @kentcdodds excellent epic-stack

• npx create-remix@latest --typescript --install --template epicweb-dev/epic-stack
• installation start the app, it should work without any problem
• close it.
• update chalk from version 4.1.2 (CJS) to version 5.2.0 (ESM) npm i -D chalk@5.2.0
• try to start the app again. it will fail, if you are on Windows

Expected Behavior

App running:

Waiting for app server (f950aa74)
> npm run dev:server
Remix dev server ready

> dev:server
> cross-env MOCKS=true tsx watch --clear-screen=false --ignore "app/**" --ignore "build/**" --ignore "node_modules/**" ./index.js

🔶 Mock server installed
🚀  We have liftoff!
Local:            http://localhost:3000
On Your Network:  http://10.100.102.21:3000
Press Ctrl+C to stop
App server took 3.5s

Actual Behavior

App not running

Waiting for app server (f950aa74)
> npm run dev:server
Remix dev server ready

> dev:server
> cross-env MOCKS=true tsx watch --clear-screen=false --ignore "app/**" --ignore "build/**" --ignore "node_modules/**" ./index.js

🔶 Mock server installed

[onemen]

There is an easy fix

updating this code fix the issue

remix/packages/remix-dev/devServer_unstable/index.ts

Lines 69 to 79 in 761fc1d

	let newAppServer = execa.command(command, {
	stdio: "pipe",
	env: {
	NODE_ENV: "development",
	PATH:
	bin + (process.platform === "win32" ? ";" : ":") + process.env.PATH,
	REMIX_DEV_HTTP_ORIGIN: stringifyOrigin(httpOrigin),
	},
	// https://github.com/sindresorhus/execa/issues/433
	windowsHide: false,
	});

    let newAppServer = execa.command(command, {
-     stdio: "pipe",
+     stdio: ['ignore', 'pipe', 'pipe'],
+     shell: true,
      env: {
        NODE_ENV: "development",
        PATH:
          bin + (process.platform === "win32" ? ";" : ":") + process.env.PATH,
        REMIX_DEV_HTTP_ORIGIN: stringifyOrigin(httpOrigin),
      },
      // https://github.com/sindresorhus/execa/issues/433
      windowsHide: false,
    });

EDIT

• It work also without adding shell: true,
• it WORK with stdio: ['inherit', 'pipe', 'pipe'] or stdio: ['ignore', 'pipe', 'pipe']
• it DOES NOT WORK with stdio: ['pipe', 'pipe', 'pipe']
• using the same script without watch also work. remix dev -c "tsx ./server.js"
• any colors added to console.log in the server code are stripped out somewhere...
  setting stdio: ['inherit', 'inherit', 'inherit'], fix the color issue

[xHomu]

Ah, that explains why I couldn't get tsx watch to work on Windows.

Can confirm the fix solved it!

[xHomu]

Seems like Epic Stack resorted to a hack using execa, but this should really be fixed upstream on @remix-run/dev, since this affects everyone who want to use v2 dev server on Windows with tsx.

https://github.com/epicweb-dev/epic-stack/blob/main/server/dev-server.js#L9

[pcattori]

Closing as this seems to be a bug in tsx, not Remix (#6538 (comment))

[onemen]

There is already a PR in tsx to fix this issue