Init project failure
See original GitHub issueStarted like this:
➜ rootDir npm install -g create-graphql-server
/Users/me/.nvm/versions/node/v6.9.1/bin/create-graphql-server -> /Users/me/.nvm/versions/node/v6.9.1/lib/node_modules/create-graphql-server/dist/bin/create-graphql-server.js
/Users/me/.nvm/versions/node/v6.9.1/lib
└── create-graphql-server@0.5.1
Error:
➜ rootDir create-graphql-server init generator
env: babel-node: No such file or directory
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Why projects fail: 7 reasons (and their solutions) - Asana
Project failure happens, but it's often avoidable. Learn how to prevent these common pitfalls and set your projects up for success.
Read more >Top 10 Reasons for Project Failure (And How to Prevent Them)
Inadequate resource forecasting is a leading cause of project failure over 20% of the time. When resources are not enough, the imbalance between ......
Read more >npx react-native init project failure while installing Bundler ...
Description Hello, I am trying to initialize a new project by following the steps in Setting Up the Development Environment.
Read more >Error 'Initialize Project Area' failed when creating a ... - IBM
You receive error 'Initialize Project Area' failed when you create and save a project in IBM Engineering Workflow Management (EWM).
Read more >5 common reasons for project failure within agencies and how ...
The main reasons why projects fail over and over again. Figuring out why a project has failed is like popping the hood of...
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
Fixed in 0.5.3
This sounds like a bug though, I don’t think you should have to do that.