npm install/start not working properly when path contains '%'?
See original GitHub issueCan 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
npm ls react-scripts
(if you haven’t ejected): `-- react-scripts@1.0.7node -v
: 6.9…5npm -v
: 5.0.0
Then, specify:
-
Operating system: Windows 10
-
Browser and version: Firefox and Chrome (latest)
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (8 by maintainers)
Top GitHub Comments
Closing as fixed.
Ooh nice. Let us know when it makes it into a stable release!