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

biutiful

v0.4.6

Published

Biutiful is a clever little CLI tool for transforming npm dependency trees into JavaScript import/export modules.

Downloads

8

Readme

Biutiful

Biutiful transform ES imports into browser usable ECMAScript imports.

Getting Started

Using the command requires supplying the input directory which contains your source files in their original format, followed by the output (defaults to ./) directory which is where all of the files and ES modules will reside.

For example, to take the files from ./src and to write to ./public you'd supply the following:

biutiful --input ./src --output ./public

All of the dependencies found within node_modules will be placed into the es_modules directory, and have their imports updated – along with the source files – to map to the ES files using Babel's AST parser.

When traversing dependencies, Biutiful will attempt to find ES modules from the package.json file using the module and js:next entries respectively. If neither are found then either the main entry or ./index.js file will be used and the file(s) transpiled using Lebab.