Update environment requirements without making a new virtual environment #25

mehcode opened this Issue Dec 4, 2012 · 4 comments

4 participants


First off I want to say 👍 awesome stuff here.

I would appreciate the ability to modify the requirements.txt file and instruct nodeenv to update my "global" requirements without having to destroy and rebuild the environment.


I've been using --force for that.


@kylehayes can you elaborate? I don't see that option documented anywhere.


@shellscape, you're going to make me remember that far back :-P
Looking at my notes it looks like I used it like so:
nodeenv --requirement=./requirements.txt --jobs=4 --force env


I think that both of these options (--force and --update) can coexist together.

@ekalinin ekalinin closed this in ccf3a4b Feb 9, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment