npm install from github wrong package name

This will give you a tgz file like percy-cypress-1.0.5.tgz. To prepare a binary file, run npm pack command (without -dry option). When you make a GitHub release you can drop binary files there. Now, push the code (using a separate branch for example) to GitHub. Npm notice integrity: sha512-NA75z/sUCpZLRgmy9ZyI3rQo8Q= After adding files: we get just the necessary file list. Lots of stray files - no user of this NPM package needs tslint.json for example. Npm notice integrity: sha512-PoLpQJbOCd+2p9rS2kGW/MQv0A= Npm notice filename: percy-cypress-1.0.5.tgz In our case, we want to only distribute the dist folder with the NPM package. npmignore since when using files you can whitelist or blacklist files and folders. 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.

Npm install from github wrong package name