Edit: Cameron Tacklind has written an excellent answer detailing how to do this: There might be another way to do this using a prepare script, but I'm not sure if that's possible I've never tried it. You then should be able to install from github. (Ensure that you have run npm install first) It's ugly, but in this case you will have to remove dist/ from the. dist/ is built from the files in src/ before the package is published to the npm registry, but dist/ is never committed to the repo. Your problem is that in your case, dist/ is not committed to the repo (since it is in the. npmignore file.ĭon't panic if the install command takes a long time installing from a git repository is slower than installing from the npm registry. If that isn't working correctly, check the contents of your. You will most likely want to use the -save or -save-dev flag with the install command to save dependency in your package.json. Try npm install /, where is your GitHub username (without the and is the name of the repository. It seems like it could be a common enough issue when modifications need to be made to a package's source code? Maybe there's a better solution? Would love to get some feedback on this issue. I don't have a huge amount of experience with npm. I apologise for my ignorance on the topic. I've also tried publishing the fork as my own module to the npm registry, but again I get no build, and I'm not sure that's the right thing to do. I've seen some dicussion of running the prepublish script, but I'm not sure how to do this when installing all the modules. The second npm install gives me the full repo, but again I don't get a build like when I use the command npm install angular-translate. npmignore, and some markdown files -angular-translate The first gives me a directory like this with no build. A colleague suggested that I fork the repo of the source code and point to my forked repo as a dependency, which I've tried in these ways, e.g. However, I've had to make a few small modifications to the source code to get everything working the way I'd like, and now I want to persist those changes on npm install.
I'm using a module for my angular app called angular-translate.
0 kommentar(er)
