So here is how to do this myself.įirst, add the files: property to the package.json. rw-r-r- 1 gleb wheel 1878 Apr 1 22:59 package.json rw-r-r- 1 gleb wheel 627 dependencies.yml I could simply install my fork using github: reference 1īut this installation installs. Meanwhile I wanted to use my patched version in bahmutov/calculator project. I have opened a pull request with my work around from my fork bahmutov/percy-cypress branch find-percy-58. ![]() Today I had just this problem - I needed to quickly patch NPM module to get around Webpack bundling problem there. but that is tricky, since the project might be a pain to build. If we just install an NPM package from GitHub we will not get the dist folder - it is not on GitHub. The built dist folder is the one published to the NPM registry. The GitHub repository only has the lib folder with the original source. ![]() More and more NPM packages are now transpiled from TypeScript for example, and thus usually have two folders: lib and dist. But that blog post had a huge shortcoming - it did not deal with built or transpiled artifacts. I have discussed how to Use GitHub instead of NPM to share and install NPM modules.
0 Comments
Leave a Reply. |