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/assets

v1.10.1

Published

The static assets (images, code, etc.) for the CoCalc frontend.

Downloads

60

Readme

Static Webapp Assets

This code is part of https://github.com/sagemathinc/cocalc and isn't currently designed to be used standalone.

TODO: This module is called "assets" so you immediately think "I better not put things other than assets here", and usually "assets" refers to static assets in the context of web application.


This sub-directory contains assets (images, code, etc.) for the frontend and static pages.

Compute Environment

Here is a description of two optional files describing the content of the computational environment (programming languages, libraries, ...)

Do this if you want to test rendering with the full production data for compute-*.json:

~/cocalc/src/packages/assets$ curl https://storage.googleapis.com/cocalc-compute-environment/compute-components.json > compute-components.json
~/cocalc/src/packages/assets$ curl https://storage.googleapis.com/cocalc-compute-environment/compute-inventory.json > compute-inventory.json

Do NOT commit this to the repo. It's unlikely you accidentally will, because neither file is in the cocalc git repo.

compute-inventory.json

This is the "ground truth" of what is installed in the environment. Layout:

{
 "language_exes":             map of a full executable path to this dictionary:
   {
   "path to executable":
     {
       "doc"   : documentation string
       "lang"  : language (python, R, ...)
       "name"  : Anaconda R
       "url"   : website
     },
   "another path to a language executable":
     { ... }
   }

For each such language and executable path:


  "language name" : e.g. "python"
    {
    "path to executable" : defined in the dictionary above
      {
        "library 1" : "version"
        "library 2" : "version"
        ...
      },
    "path to another executable of that language":
      { ... }
    },
  "another language":
    { ... }
  }
}

compute-components.json

This JSON dictionary contains descriptions of each library. It is hand curated or autogenerated from databases. Note, there can be several instances of the same library being installed in the inventory file, while this description file only lists it once.

{
 "language": {
   "library name": {
     "descr"        : "long description of the library",
     "doc"          : "documentation URL",
     "name"         : "Name",
     "summary"      : "short summary",
     "url"          : "website"
   },
   "library 2": { ... }
 },
 "another language" : { ... }
 "executables": {     # special language listing all executables with their full path
   "/bin/bash": {
     "name": "Bash",
     "..." : ...
   }, ...
 }