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.

ActionHero Generate and Yarn don't play nicely

See original GitHub issue

Description of Issue

ActionHero Version: ^16.0.0
Node.js Version: v7.2.0
Operating System Ubuntu 16

Steps to reproduce your error

Make a new actionhero project with ./node_modules/.bin/actionhero generate
npm start

And I’ve got:

npm ERR! Linux 4.4.0-53-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
npm ERR! node v7.2.0
npm ERR! npm  v3.10.9

npm ERR! missing script: start
npm ERR! 
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

Issue Analytics

State:
Created 7 years ago
Comments:9 (5 by maintainers)

Top GitHub Comments

2reactions

evantahlercommented, Dec 10, 2016

I personally don’t like 1 or 2. actionhero generate is a new project generator. If you already have a package.json, you aren’t running the generator to create a new project! To that end, the generator does what it can, and won’t touch any of your existing files.

If you have ActionHero installed globally, #2 sort of already works… you just need to be inside your new project directory.

You should never install any node package globally ever under any circumstances. What happens when versions change and separate projects you have want separate versions? But… that’s just my opinion.

This would be a great thing to discuss in our slack room. http://slack.actionherojs.com/

0reactions

evantahlercommented, Mar 3, 2017

Closing, because this isn’t really about Yarn, but about global packages and overwriting things.