embark doesn't detect itself in devDependencies
See original GitHub issueBug Report
Summary
embark only detects itself when listed in package.json dependencies, not devDependencies
Current behavior
running npx embark -h
throws the error:
embark ERR! Could not find embark specified in "dependencies" or "devDependencies" of local package.json file
Please provide additional information about your system
OS: Embark Version: 4.0.0-alpha.3 Node Version: NPM Version:
Sometimes issues are related to Embark’s installation. Can you provide information on how Embark was installed?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
embark doesn't detect itself in devDependencies · Issue #1231 ...
Bug Report Summary embark only detects itself when listed in package.json dependencies, not devDependencies Current behavior running npx embark -h throws ...
Read more >FAQ - Embark
While Embark can detect over 210 genetic variants associated with increased disease risk, we cannot provide medical diagnoses. You should talk to your...
Read more >Monorepository and conflicting dependencies - Ember CLI
Let's embark on a deep dive into how npm and webpack work, see how ... Move app dependencies to devDependencies; In root package.json....
Read more >An Effective Python Environment: Making Yourself at Home
You'll see a verbose list of all the dependent software conda will install, and it will ask you to confirm. conda doesn't have...
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 FreeTop 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
Top GitHub Comments
This was fixed in master a week or two ago, so yes, it will be in the next beta release.
Closing this as v4 stable had been published