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

tokamak

v0.0.15

Published

Tokamak bundler

Downloads

31

Readme

tokamak

Isomorphic self-bundling bundler

Why CJS

In Tokamak, contrrary to the current trent in JS, we made the choice to convert all modules to the CJS format (and not ESM). There are several reasons for this choice:

  • There's still a ton of NPM modules out there which are only available in CJS, while totally working in a browser
  • It is much easier to isolate CJS modules for the purpose of automatic HMR

This choice comes with a couple of drawbacks:

  • ESM style circular dependencies are not supported. We make an effort to support them as node style circular require, but this may break for some modules.
  • All exports are by value, e.g. export let foo = 'bar' cannot be modified by another module that imports it. This is a more rare situation in the wild, though we saw some modules that employ this mechanism, and they will not bundle either.

How things work

Static part produces an in-memory file-system like snapshot - the require graph Dynamic part produces a require function that can be passed to a CJS module instantiator in the browser, and, given the require graph "file system", implements the Node CJS resolution algorithm. ... to be continued...