Set aliasify configDir to correct value.

[jmm]

This fixes the problem illustrated in this example.

remapify is aggregating aliases from all of the patterns, and pointing the aliases to paths relative to process.cwd(), but then passing the src from one of the patterns to aliasify as configDir. To do things the way the plugin is setup to do them, all of the paths the aliases point to need to be relative to the same dir that's passed as aliasify's configDir.

The tests continue to pass after this change, but they also passed before the change when this was broken. How do you suggest going about testing that remapify generates the correct data and configuration for aliasify?

[joeybaker]

@jmm Thanks! I really appreciate you being so active on this project – thank you!

Somewhere along the way mocha (or more likely browserify), stopped being a PIA, and this test now runs. Uncomment it and you have a full integration test (I've done this in a branch I'm working on to fix the pipeline changes of browserify). Would that do it for you?

[jmm]

@joeybaker Thanks, I'll take a look at that test. I might have a lead on a solution to the pipeline issue as discussed in my latest comment on #26.

[joeybaker]

@jmm awesome! Thanks for all the work!

[tommoor]

Any word on this guys? Just lost over an hour to trying to get remapify to work and this branch ended up fixing it.

[joeybaker]

v2 of remapify was just released and aliasify is no longer used. Please give that a try and see if your issue is solved. In the meantime, I'm going to close this PR since it modifies code that is no longer in the project.