Skip to content
This repository has been archived by the owner on Mar 4, 2022. It is now read-only.

BUG: Fix PATH/NODE_PATH resolution order. #48

Merged
merged 1 commit into from Dec 9, 2015
Merged

Conversation

ryan-roemer
Copy link
Member

Fixes #47

We now have a more sensible PATH / NODE_PATH resolution order.

Also:

  • Update links on HISTORY
  • Minor flags fix for builder run

/cc @dandelany @boygirl @exogen @chaseadamsio

@dandelany @boygirl @exogen -- Can one of you try this out in an erroring Victory repo? Thanks!

@@ -142,7 +142,7 @@ Task.prototype.run = function (callback) {

var env = this._env.env; // Raw environment object.
var task = this.getCommand(this._command);
var flags = args.concurrent(this.argv);
var flags = args.run(this.argv);
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BUGFIX

@dandelany
Copy link

Just checked out this branch and it does indeed fix the error I was seeing. Running babel --version in the builder task now correctly shows the local node_modules babel version. Also did a quick code review and everything looks fine 👍 . Thanks!

ryan-roemer added a commit that referenced this pull request Dec 9, 2015
BUG: Fix PATH/NODE_PATH resolution order.
@ryan-roemer ryan-roemer merged commit ebaa822 into master Dec 9, 2015
@ryan-roemer ryan-roemer deleted the bug-node-resolve branch December 9, 2015 15:00
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Builder scripts using global npm dependencies instead of locals
2 participants