npm-publish | 易学教程

npm publish - removing scripts from package.json?

阅读更多关于 npm publish - removing scripts from package.json?

问题 Before publishing my script, I have a number of scripts under the package.json to compile coffeescript, typescript and developer only commands - which make no sense once it's published. I was wondering if there is a procedure for removing certain scripts under the package.json ? Considering that when publishing your package, it also publishes package.json. Would this be possible to kind of remove scripts before publishing the package? Once I publish my script, I remove a lot of the typescript

Getting 404 when attempting to publish new package to NPM

阅读更多关于 Getting 404 when attempting to publish new package to NPM

I just created a new package: https://github.com/supericium/pli I'm now trying to publish it to NPM for the first time like this: ole@MKI:~/Sandbox/pli$ npm publish --access public npm ERR! publish Failed PUT 404 npm ERR! Linux 3.13.0-93-generic npm ERR! argv "/home/ole/.nvm/versions/v6.4.0/bin/node" "/home/ole/.nvm/versions/v6.4.0/bin/npm" "publish" "--access" "public" npm ERR! node v6.4.0 npm ERR! npm v3.10.3 npm ERR! code E404 npm ERR! 404 Not found : @supericium/pli npm ERR! 404 npm ERR! 404 '@supericium/pli' is not in the npm registry. npm ERR! 404 You should bug the author to publish it

How to generate NPM release candidate version

阅读更多关于 How to generate NPM release candidate version

Say I want to generate a pre-release NPM version. Originally I have this: "version": "0.0.1" I tried: npm version prepatch npm version prepatch npm version preminor npm version preminor that gave me this: v0.0.2-0 v0.0.3-0 v0.1.0-0 v0.2.0-0 Those don't look useful to me, because they always bump up the actual version number, meaning npm version patch and npm version prepatch don't seem to be making much difference. So my question is - is there an official way to generate an alpha/beta version with npm at the command line? npm version minor-alpha npm version minor-beta npm version minor-rc

npm install and build of forked github repo

阅读更多关于 npm install and build of forked github repo

This is not a totally new question, but I've been looking around for a good while now and I'm having trouble finding a solution. I'm using a module for my angular app called angular-translate. 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 . 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. npm install https://github.com/myRepo/angular-translate npm install https://github.com

npm install and build of forked github repo

阅读更多关于 npm install and build of forked github repo

问题 This is not a totally new question, but I\'ve been looking around for a good while now and I\'m having trouble finding a solution. I\'m using a module for my angular app called angular-translate. 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 . 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