-
Notifications
You must be signed in to change notification settings - Fork 97
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
Allow using a fork instead of an npm package or patch #217
Comments
First, thanks for pointing this use case, I never used it and just discovered the I tried to install from git using a subfolder with NPM but sadly it is not possible at now 😢 here is the issue : npm/npm#2974 |
Thanks for the info. I'm currently using a patch of a local version I created. |
Sorry for that, we have a lot of work to do simultaneously of this project. |
Current implementation of this package does not allow contributor to test their fork before submitting a pull request.
Since in
next
version the dist folder is no longer checked-in (which is good) one cannot fork and usenpm install git+...
.In the npm documentation there's a
prepare
script that might facilitate for this.However, since the repository has two goal - the library and the example it creates a problem for this.
One solution is to split this to two repositories - one for the example and the other for the library, the other option is to force the
prepare
script to copy/remove files in order to be able to create the library so it will be possible to reference it.I don't have a magical solution, I just want to be able to use my fork without creating an npm package.
If you are familiar with other solutions I would love to hear.
The text was updated successfully, but these errors were encountered: