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

yuck

v1.1.1

Published

yuck.js -- The browser bundler for smart people === webpack? rollup? parcel? blah blah?

Downloads

6

Readme

yuck.js -- The browser bundler for smart people

webpack? rollup? parcel? blah blah?

All of them require packing in development.

How the heck am I supposed to use the amazing chrome debugger?

Enter yuck.js

Now we can actually use commonJS modules, in the browser, without packing.

Debugging has never been easier.

Two-way live reload, using Chrome's built in local workspace feature; is so incredibly useful. Why do we not embrace it?

Installation

  npm install --save yuck

Usage

  yuck deps -o ./build/deps.js ./index

Then in your main HTML file, simply include yuck and your deps file and require your entry point:

  <script src="node_modules/yuck/yuck.js"></script>
  <script src="build/deps.js"></script>
  <script>require('./index')</script>

That's it, yuck will take care of everything else and actually load the files you wrote. No more transpiling, no more bundles, just pure unadulterated old school cool.

Production

No bundler, or in this case non-bundler, would be complete without a way to actually bundle. You can use browserify for this, but I really dislike their include the world approach. So there is:

  yuck pack -o build/app.js ./index

The bundle includes a slimmed down yuck prolog to support commonJS modules, so there is no other code to require:

  <script src="./build/app.js"></script>

Note: the packed version automatically evaluates your entry point, so no need for the explicit require('./index') that you'd need in dev mode.