The Frontend doesn't work on Windows 10 about substrate-front-end-template

[koalyptus]

@danforbes @Mereep,
adding the PORT variable to the .env file at root:

EXTEND_ESLINT=true
PORT=8000

and modifying the start command in package.json to read:

...
  "scripts": {
    "start": "react-scripts start",
...

was enough to make it work under windows.

[Mereep]

I could resolve the second issue by:

• purging yarn cache
• manually installing babel/helper-call-delegate using npm i @babel/helper-call-delegate
• using npm install (instead of the documented yarn install)

However, I don't know if step 1 was necessary. Someone might go into details. However, the documentation should reflect that. Installling all of that tool chains is already quite a pain.

Also, I am not too much into those node package managers, but npm and yarn seem quite interchangeable. Why having the user install yarn when npm is doing the job?

[JoshOrndorff]

So you have the UI running successfully now?

Did you try running yarn install and get an error? If so, please share the error. If you never ran that command, then I'm not surprised it didn't work, you have to install the dependencies first.

PORT=8000 react-scripts start works fine in bash on linux. Maybe it doesn't work on Windows. What shell are you using? cmd.exe? power shell? gitbash?

[danforbes]

Yeah, I think this is Linux-type syntax for passing an environment variable into a command. It makes sense this would break on Windows. We may want to look into using a library like dotenv to help with this.

[Mereep]

So you have the UI running successfully now?

yes

Did you try running yarn install and get an error?

I used yarn install, it installed successfully. Error happens after start.
However, after using npm install instead, I could start it afterwards

What shell are you using?

cmd