Quitting react dev server closes browser and any open tabs

[nikolas]

This only occurs if create-react-app creates the browser process itself. See info below.

Environment

1. node -v: v6.11.3

2. npm -v:5.4.1

3. yarn --version (if you use Yarn):

4. npm ls react-scripts (if you haven’t ejected): react-scripts@1.0.12

5. Operating system: Ubuntu 16.04

6. Browser and version (if relevant): Chromium 60.0.3112.113

Steps to Reproduce

1. Without a browser open, run npm run start in a repo created with create-react-app
2. Open a few tabs in the browser created by that command.
3. Ctrl-C the react server.

Expected Behavior

The browser remains open. Or maybe gives a confirm dialog, then closes.

Actual Behavior

The browser closes, losing my open tabs.

[Timer]

That's not desirable!
If possible, could you look into this and fix the spawning of the process so it's not killed when its parent dies?

[GAumala]

I did notice this issue a couple months ago. The problem is that spawning the browser child process is handled by the opn module, which is very useful to abstract little details of different operative systems, but does not expose much options to detach the child process from the original process.

I tried sending a pull request with a possible solution, but I didn't got a response in time so I moved on to different matters.

[evalexpr]

This doesn't seem to happen for me:

node -v: v8.5.0

npm -v:5.4.1

yarn --version (if you use Yarn): 1.0.1

npm ls react-scripts (if you haven’t ejected): react-scripts@1.0.11

Operating system: macOS Sierra

Browser and version (if relevant): Chrome Version 63.0.3215.0

EDIT: I've since tried this on Arch Linux with Chromium 61.0.3163.79, node 8.5.0, npm 5.3.0, & react-scripts@1.0.13 and can confirm this behaviour (have also confirmed on opn repo) 👍

[GAumala]

Thanks @W1lkins for confirming the issue in the opn repo. The PR with the fix has been merged, so let's wait until they make a release and update the opn version in react-scripts.

[chrifox]

Hi I am having this same issue on Ubuntu 16.10 running node v6.11.1, is there a workaround until a fix is released?

[GAumala]

I think the easiest workaround is to have your browser up and running well before starting the dev server.

If the browser is an independent process, it won't be closed when the dev server is interrupted.

[gaearon]

I bumped opn to the latest which includes your fix so this should be solved in the next release.
#3784