You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
Is there any reason why you dont pass paths in loadTransforms?
I had some transforms installed in a separate directory referenced by NODE_PATH. node find them correctly but browserify not even if I pass that directory to the paths option of browserify.
I went down the calls until I found that the missing piece is to add paths: self.paths to the params variable in loadTransform.
By doing that, it now works but I don't know if this is the right solution.
The text was updated successfully, but these errors were encountered:
I've never used NODE_PATH and haven't got a clue, but it sounds like people who do use it generally expect it to apply to transforms too, so we should probably land one of the existing PRs that implements this.
I've seen there is already PRs for exactly this subject.
Both PRs have made the exact same modification as the one I made. #120 contains test code. #92 solves an another error: Error message will always contain undefined since it references the wrong variable.
If you should only accept one, then #120...
Hi,
Is there any reason why you dont pass paths in loadTransforms?
I had some transforms installed in a separate directory referenced by NODE_PATH. node find them correctly but browserify not even if I pass that directory to the paths option of browserify.
I went down the calls until I found that the missing piece is to add paths: self.paths to the params variable in loadTransform.
By doing that, it now works but I don't know if this is the right solution.
The text was updated successfully, but these errors were encountered: