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

beck

v0.1.0

Published

An ES6 Module Loader pipeline toolkit and shim.

Downloads

10

Readme

beck.js

This is a work in progress

beck.js is a toolkit for building ES6 Module Loader pipelines as well as an ES6 Module Loader shim for legacy environments.

The shim deviates from the spec in various ways. It does this when the spec seems to do strange things or makes it really difficult to do common things -- things we've been doing with javascript modules since 2007.

This isn't ready for use, yet.

This project probably isn't ready for you to try out, yet. It only understands CommonJS modules that have not been concatenated using some sort of transport format (browsers) and has onlly been rudimentally tested in modern browsers, node.js, and RingoJS.

Stay tuned for further updates.

Loader behavior

  • Sense if environment has an ES6 loader already
    • If not, stub one asap
  • Await first require/request or config() call
    • If config()
      • Ensure amd, cjs, or es6 shims are properly installed
      • If main, loader.load(main)
    • If require() or data-beck-run
      • If no config has been set for this module, sniff for package.json at every folder in path to module, starting at deepest and ending at document's folder (also: bower.json and beck.json)
      • Ensure amd, cjs, or es6 shims are properly installed
      • System.load(module)
  • Config could also be supplied in an HTML data-* attr

Open questions

  • How does beck wait for first require/request or config() call in node/ringo?
    • ENV var?
    • System.load/import