npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

getcdn

v0.0.1

Published

Save the cdn file completely locally.

Downloads

2

Readme

getcdn

Save the cdn file completely locally.

why do you need it

Because the cdn may be unstable, or it needs to be deployed in an intranet environment. At this time we need to download the cdn file to the local.

Suppose you use such a cdn file:

<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/[email protected]/dist/css/bootstrap.css">

Then you downloaded it directly through the browser and saved it as bootstrap.css , and then referenced the file you just downloaded in the project, which seems to be fine, but there are actually many hidden dangers:

  • When bootstrap.css runs a certain function, it needs to depend on ./bootstrap.font, because you didn't know it before, so you didn't download it, which caused an error (the related dependencies were not downloaded).
  • During use, you find a problem and need to consult the bootstrap documentation, but you don't know what version to check (some libraries do not mark their own version number in the file).
  • When you need to switch back to the third-party CDN again, you will find how happy it is if you only need to change one origin (full mirror URL).
  • the url you want to trace to its github, its other versions, and more information about it...

how to use

Command Line:

# install
npm i -g getcdn

# help
getcdn .help

# download the latest version
getcdn jsonkey

# Specify the storage directory
getcdn .dir=mycdn jsonkey

# Download the specified version
getcdn [email protected]

# Specify namespace and version
getcdn @wll8/[email protected]

License

MIT

Copyright (c) 2017-present, xw