| sass_binary_site=https://cdn.npmmirror.com/binaries/node-sass | |
| disturl=https://registry.npmmirror.com/dist | |
| profiler_binary_host_mirror=https://cdn.npmmirror.com/binaries/node-inspector/ | |
| fse_binary_host_mirror=https://cdn.npmmirror.com/binaries/fsevents/ | |
| phantomjs_cdnurl=https://cdn.npmmirror.com/binaries/phantomjs/ | |
| electron_mirror=https://cdn.npmmirror.com/binaries/electron/ | |
| chromedriver_cdnurl=https://cdn.npmmirror.com/binaries/chromedriver | |
| operadriver_cdnurl=https://cdn.npmmirror.com/binaries/operadriver | |
| selenium_cdnurl=https://cdn.npmmirror.com/binaries/selenium | |
| node_inspector_cdnurl=https://cdn.npmmirror.com/binaries/node-inspector |
I was poking around trying to figure out all the packages I have access to publish and got curious. So I write this little script to determine the download stats for all the packages I have publish access to.
Feel free to try it yourself. Just change the username passed to getUserDownloadStats.
By default, the stats are sorted by their average daily downloads (descending). That should give you an idea of the most "popular" package of a given user relative to how long that package has been around.
You can use it with npx like so:
| srcfile=$1 | |
| dstfile=$(basename $srcfile .svg).ico | |
| convert -density 256x256 -background transparent $srcfile -define icon:auto-resize -colors 256 $dstfile |
- HTTP 形式：
git clone https://github.com/owner/git.git
- SSH 形式：
git clone git@github.com:owner/git.git
A brief example on how to use npx to run gist based scripts.
Read the article here https://neutrondev.com/npm-vs-npx-whats-the-difference/ or watch it on YouTube https://www.youtube.com/watch?v=fSHWc8RTJug
国内从 Docker Hub 拉取镜像有时会遇到困难，此时可以配置镜像加速器。Docker 官方和国内很多云服务商都提供了国内加速器服务。
Dockerized 实践 https://github.com/y0ngb1n/dockerized
Ubuntu 16.04+、Debian 8+、CentOS 7+
| # package-lock=false | |
| registry="https://registry.npm.taobao.org" | |
| disturl="https://npm.taobao.org/dist" | |
| nvm_nodejs_org_mirror="http://npm.taobao.org/mirrors/node" | |
| nodejs_org_mirror="http://npm.taobao.org/mirrors/node" | |
| sass_binary_site="http://npm.taobao.org/mirrors/node-sass" | |
| electron_mirror="http://npm.taobao.org/mirrors/electron/" | |
| SQLITE3_BINARY_SITE="http://npm.taobao.org/mirrors/sqlite3" | |
| profiler_binary_host_mirror="http://npm.taobao.org/mirrors/node-inspector/" | |
| node_inspector_cdnurl="https://npm.taobao.org/mirrors/node-inspector" |
React recently introduced an experimental profiler API. After discussing this API with several teams at Facebook, one common piece of feedback was that the performance information would be more useful if it could be associated with the events that caused the application to render (e.g. button click, XHR response). Tracing these events (or "interactions") would enable more powerful tooling to be built around the timing information, capable of answering questions like "What caused this really slow commit?" or "How long does it typically take for this interaction to update the DOM?".
With version 16.4.3, React added experimental support for this tracing by way of a new NPM package, scheduler. However the public API for this package is not yet finalized and will likely change with upcoming minor releases, so it should be used with caution.