-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specifying a forked npm package is not possible #4455
Comments
"How can I do this?" questions are best posed on StackOverflow or the Meteor forums, not our bug tracker.
So
should do the trick. |
I did ask this question over on stackoverflow. (no response) Plus the error message indicated that it may not be possible to directly reference the npm fork/branch. Npm.depends() does not exist in the main code base. Npm.depends() only exists when processing a meteor package. It looks like you are saying that I need to create a fake meteor package to wrap the the forked npm package. So I can't just point the packages.json at the location like I can in package.json in a plain node project? |
Because that is how the Meteor platform's npm integration was designed. |
Just to use a fork of a npm library requires:
Maybe this could be improved? |
(You can also answer it over here: http://stackoverflow.com/questions/30466824/in-meteor-how-to-use-a-npm-library-that-should-be-pulled-from-a-repository )
In my packages.json file, I have:
because I need to use a forked ( and fixed version of the library). The above syntax works in straight node. How to do this in meteor?
This is the error I get:
I tried removing the line and using meteor add to get the package included:
Failed:
Failed:
Failed:
Failed:
The text was updated successfully, but these errors were encountered: