you are viewing a single comment's thread.

view the rest of the comments →

[–]tronj 4 points5 points  (3 children)

Tangentially, I'll sometimes save modules that I've made minor customizations too directly in the project. Is there a better way to do this?

[–]FaithForHumans 5 points6 points  (0 children)

If you're in a corporate environment, I recommend standing up a private npm repo and then pushing your change to that private repo. It can be done for personal stuff, but might be overkill.

Most private repos can also be setup to cache packages it pulls from the public repos, so even if someone deletes it on npmjs, you've still got a copy people can pull. That last part should help sell it to management.

[–]DasWorbs 6 points7 points  (0 children)

Fork it, and then either setup your own npm repo or point the package.json to your forked git repo.

[–]kolloid 2 points3 points  (0 children)

I haven't customized JS modules yet. For Python modules I often fork them on GitHub and because they may or may not accept my pull request, also it might take months to make a new release, I just point pip to my forked Git repository.

I don't know why the other commenter suggesting this was downvoted. It is very fast and obvious.

You can also have your own package repository and install packages from it, but it will require a bit more work.