question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

The Frontend doesn't work on Windows 10

See original GitHub issue

Hello,

I just followed the workflow given here and here to install substrate onto my (Windows 10)-Machine.

The Node - after quite some attempts - could compile and run successfully. So I followed the tutorial further which brought me here in order to install the substrate frontend template.

I could however not make it run, since yarn run start will fail with

yarn run start
yarn run v1.22.0
$ PORT=8000 react-scripts start
Der Befehl "PORT" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.

(complaining trying to run PORT which is not a command). After a bit googling, I found that it will basically run that line: "start": "PORT=8000 react-scripts start" which according to the Yarn-Docs just runs the PORT command (which is not available).

So I removed that part (in the hopes its meant as some parameter and has a reasonable default value), which actually made the server start. However, when attempting to access the web ui, it spills me an error:

Error: Child compilation failed:
  Module build failed (from ./node_modules/react-scripts/node_modules/babel-loader/lib/index.js):
  Error: [BABEL] C:\Users\xyz\dev\substrate_frontend\node_modules\webpack\buildin\global.js: Cannot find module '@ba  bel/helper-call-delegate'
  Require stack:
  - C:\Users\Richard\dev\substrate_frontend\node_modules\babel-preset-react-app\node_modules\@babel\plugin-transform-par  ameters\lib\params.js

which made me finally report here: I guess thats not suppose to happen.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5 (2 by maintainers)

github_iconTop GitHub Comments

2reactions
koalyptuscommented, Jul 8, 2020

@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.

0reactions
Mereepcommented, Jun 16, 2020

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

Read more comments on GitHub >

github_iconTop Results From Across the Web

Windows 10 apps open but do not display on desktop
Press Windows + X keys on the keyboard and select Control Panel · Type Troubleshooting in the search bar on the Control Panel....
Read more >
yarn command doesn't work on Windows 10: Here's a fix. #21
yarn command doesn't work on Windows 10: Here's a fix. ... I was able to complete the yarn command, run npm start successfully,...
Read more >
[SOLVED] Frontend Login does not work in IE on Windows 10
Logging in to the frontend on my Joomla 3.6.5 site in Internet Explorer on Windows 10 as a normal user just returns back...
Read more >
Headphone Jack Not Working in Windows 10 - How to Fix ...
When any hardware device stops working, my first recommendation is to update its drivers. Updating your Windows 10 OS could install the ...
Read more >
How to troubleshoot when Windows 10 won't update
If you're having problems getting a Windows update to work, then the first thing you should do is reboot the endpoint. Although starting...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found