Latest npm package is not working
See original GitHub issueHi @toddbluhm I’m using your npm package in react js application. it is not working properly I used below steps:
-
Install package locally
npm i env-cmd -
In package.json looks like

-
Created a .env-cmdrc file in the root directory and structure as

-
Finally updated scripts object in package.json file like

-
run the below commond
npm start -
Got the below error

Please let me know if I’ve missed out anything.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:10 (4 by maintainers)
Top Results From Across the Web
node.js - npm update does not do anything
Running npm outdated will allow you to check all the packages that need to be updated. The list will show current, wanted and...
Read more >5 Ways to Fix the Npm Install Not Working Issue
Way 1. Make Sure Npm Is Installed · Way 2. Make Sure There Is a Package.json File · Way 3. Delete Lock File...
Read more >Common errors
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 >npm does not upgrade package to the latest version #14570
I'm opening this issue because: npm is doing something I don't understand. ... npm does not upgrade package to the latest version #14570....
Read more >How to fix npm install command not working
The error above happens when npm can't be found under the PATH environment variable. First, you need to make sure that npm is...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@toddbluhm , Thank you so much for response.
Note that this error can happen if your file is broken. In my case I accidentally forgot to end a line in my .env-cmd.js file with a comma and then it started acting like the file was gone. I think the latest version is swallowing the critical part of the error. Previous version will give something like:
Current version only seems to show the “Unable to locate .rc file” part.