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

@cocalc/cdn

v1.15.1

Published

Files that CoCalc uses that would be natural in various contexts to get from a CDN

Downloads

16

Readme

Webapp Resource files

Why?

This directory contains additional resources for at least the /index.html and /app page. Many of these were served directly from CDN's before. However, that introduces a dependency where CoCalc.com can't load unless all these random CDN's also work... and that is unacceptable for two reasons:

  1. If any of these CDN's go down, CoCalc.com would get mangled or not load. That's no good.
  2. If you use a private install of cocalc on a computer that doesn't have network access, it doesn't work at all ever. That's definitely not good.

How?

Run npm ci to install the modules in the node_modules directory, as usual. The run npm run build to update the dist/ subdirectory with all relevant data ready to be served via various webservers. The setup.py script (that npm run build uses) makes sure to include a version number in the path, because all files will be served with a long cache time.

IMPORTANT: we copy all the files from node_modules to dist, rather than just making symlinks, because (1) the symlinks don't get published to npm anyways, and (2) the node_modules folders would likely get hoisted away when we install elsewhere, thus breaking everything.

Notes

Other files in packages/assets might not be used any more. At some point we can clean them up.

We have to run a postinstall script to create the versioned symlinks, since -- to be cross platform -- npm itself doesn't support symlinks.