PORT env variable not always an integer

[matoilic]

Description

When setting the PORT env variable it is a string, no matter if I set it like PORT="8088" or PORT=8088. This causes the port check in the start script if (port === DEFAULT_PORT) to always fail. port is an integer and DEFAULT_PORT a string. It also causes the kitchensink e2e test to hang.

Expected behavior

The server should start at the given port.

Actual behavior

The start script complains that something is already running on the given port.

Environment

Run these commands in the project folder and fill in their results:

1. npm ls react-scripts (if you haven’t ejected): react-scripts@0.9.0
2. node -v: v6.9.4
3. npm -v: 3.10.10

Then, specify:

1. Operating system: macOS 10.12.3
2. Browser and version: is not a browser issue

Reproducible Demo

Try starting the development server with PORT=3002 npm start

[Timer]

Hmm, odd. I can't reproduce using .env or the command line. Thanks for the report, nevertheless!

[matoilic]

I've retested it on other machines and the only one I can reproduce it on is again a Mac (El Capitan) with Bash. When using other shells or operating systems the PORT env variable is already an integer without converting it previously.