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.

npm install/start not working properly when path contains '%'?

See original GitHub issue

Can you reproduce the problem with latest npm?

Yes

Description

I deleted the node_modules of my project and then proceeded to run npm install (to check if it was ready for version control), the npm install everything until there. When I run npm start, the public/index.html is loaded but appears that the src/index.js is not evaluated, I’ve checked this with come console logs. After a a while trying to understand what was going on I noticed that a part of my project path is called ‘XXX%20-%20XX%20-%20XXX%20XXXX%20-%20XX’ with this suspicion I have changed the name of the folder and now everyhing is working ok

Expected behavior

npm start would start my app as normal with src/index.js being evaluated

Actual behavior

npm start appears to be not loading src/index.js when the project file path contains ‘%’

Environment

  1. npm ls react-scripts (if you haven’t ejected): `-- react-scripts@1.0.7
  2. node -v: 6.9…5
  3. npm -v: 5.0.0

Then, specify:

  1. Operating system: Windows 10

  2. Browser and version: Firefox and Chrome (latest)

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:8 (8 by maintainers)

github_iconTop GitHub Comments

1reaction
gaearoncommented, Jan 8, 2018

Closing as fixed.

1reaction
gaearoncommented, Jul 10, 2017

Ooh nice. Let us know when it makes it into a stable release!

Read more comments on GitHub >

github_iconTop Results From Across the Web

5 Ways to Fix the Npm Install Not Working Issue
Way 1. Make Sure Npm Is Installed ... The main cause of the npm command not found error is that npm is not...
Read more >
Npm start/install doesn't work: Npm can't find the file
Go to client folder and remove both node_modules and package-lock.json . Make sure that you have "react-scripts": "xxx" in your package.json .
Read more >
Common errors | npm Docs
Some strange issues can be resolved by simply running npm cache clean and trying again. If you are having trouble with npm install...
Read more >
package.json - npm Docs
note: Packages linked by local path will not have their own dependencies installed when npm install is ran in this case. You must...
Read more >
npm-install - npm Docs
Description. This command installs a package and any packages that it depends on. If the package has a package-lock, or an npm shrinkwrap...
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