This is in case users use npm to install instead of install.sh.
When are we launching? I don't think I'll have this ready by next Monday.
@ebidel I don't think we've nailed down a new date yet. We decided to evaluate how stable the project is before we make a call. I think you should be okay for getting this done sometime next week. No worries!
Fellas, how does the npm install -g way of installing going to work in practice? npm won't be able to run python setup.py install --quiet --force --user --install-scripts=~/.yeoman/insight no?
npm install -g
python setup.py install --quiet --force --user --install-scripts=~/.yeoman/insight
@ebidel To the best of my knowledge we wouldn't be able to run it if opting for npm install -g. Perhaps however, if someone were to fire up yeoman for the first time we could check for the existence of insight and kick off the install of it there? Would that work?
How do they get the yeomaninsight.py script then? I can figure out a way to pull it down, but this will complicate things.
That check would need to be made every time since yeomaninsight.py could have been updated and the new version needs to be installed.
Think I found a way to install the py script from package.json :)
that would be awesome :)