npmjs

Pros and cons of node-sass and gulp-sass

由 瘦欲@ 提交于 2020-01-03 08:24:12
问题 I was wondering what are the differences between node-sass and gulp-sass? What are the pros and cons of each version? I see that on www.npmjs.com node-sass has more than double of an advantage in downloads. Does this make it better? Is there a difference in compiling speed? 回答1: The difference between them is that gulp-sass has node-sass as a dependency :) gulp-sass is a plugin for Gulp - an excellent build tool. And it uses node-sass which it itself is using lib-sass which is a Sass compiler

npm publish causes 'Error: EPERM: operation not permitted, unlink …', errno -4048

由 喜你入骨 提交于 2019-12-21 03:08:18
问题 I'm trying to publish my NPM package: npm publish . I get the following quite cryptic error: npm ERR! path c:\Temp\npm-20936-b98f84c8\tmp\fromDir-02dd5394\package.tgz npm ERR! code EPERM npm ERR! errno -4048 npm ERR! syscall unlink npm ERR! Error: EPERM: operation not permitted, unlink 'c:\Temp\npm-20936-b98f84c8\tmp\fromDir-02dd5394\package.tgz' npm ERR! at Error (native) npm ERR! { Error: EPERM: operation not permitted, unlink 'c:\Temp\npm-20936-b98f84c8\tmp\fromDir-02dd5394\package.tgz'

Have I broken npm?

由 末鹿安然 提交于 2019-12-08 02:04:09
问题 I published an npm module about a day ago and have bumped the version a couple of times since then. In the beginning, there was 0.0.0, then 0.0.1, now sitting at 0.1.1. When I visit the https://www.npmjs.com/package/skipper-minio everything looks okay - versions, published date, my stupid face are all there. The 'issue' I'm seeing though, is that when you do a search that returns said module using either of the web interface at npmjs.com or the npm command line utility the version is still at

Have I broken npm?

由 自作多情 提交于 2019-12-06 11:04:28
I published an npm module about a day ago and have bumped the version a couple of times since then. In the beginning, there was 0.0.0, then 0.0.1, now sitting at 0.1.1. When I visit the https://www.npmjs.com/package/skipper-minio everything looks okay - versions, published date, my stupid face are all there. The 'issue' I'm seeing though, is that when you do a search that returns said module using either of the web interface at npmjs.com or the npm command line utility the version is still at 0.0.0, the published date is 'Invalid'/'prehistoric' and the description and other meta stuff is

Query npmjs registry via api

由 試著忘記壹切 提交于 2019-11-29 22:16:36
I find I'm often unsatisfied with the ordering and expressiveness of searches on https://www.npmjs.com/ . I guess there should be a way to programmatically query the server using https://api.npmjs.org/ or http://registry.npmjs.org/ . But how? Where is the documentation? (Or are there node packages to faciliate that? I know SO isn't about tool or package recommendations, so perhaps I shouldn't be asking about this as well, but if there were some tool, I could likely read the API from that as well.) Of course there is at least one tool designed to talk to that registry, and that is the npm

Query npmjs registry via api

由 China☆狼群 提交于 2019-11-28 18:56:35
问题 I find I'm often unsatisfied with the ordering and expressiveness of searches on https://www.npmjs.com/. I guess there should be a way to programmatically query the server using https://api.npmjs.org/ or http://registry.npmjs.org/. But how? Where is the documentation? (Or are there node packages to faciliate that? I know SO isn't about tool or package recommendations, so perhaps I shouldn't be asking about this as well, but if there were some tool, I could likely read the API from that as
订阅 npmjs