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

cujs

v0.2.2

Published

A configurable wrapper around uglifyjs

Downloads

10

Readme

cujs Build Status

[siː juː ʤeɪ ɛs] – Cosmic UglifyJS

A CLI wrapper around uglifyjs. Configurable with sensible defaults.
Make uglification ~~great~~ sane again!

It turns this

{
  "name": "awesome-lib",
  "version": "0.42.0",
  "scripts": {
    "minify": "uglifyjs dist/awesome-lib.js -mco dist/awesome-lib.min.js --comments /^!/ --source-map \"content='dist/awesome-lib.js.map',url='awesome-lib.min.js.map'\""
  }
}

into this

{
  "name": "awesome-lib",
  "version": "0.42.0",
  "scripts": {
    "minify": "cujs dist/awesome-lib.js"
  }
}

Install

$ npm i -D cujs uglify-es

Instead of uglify-es, you can install any other package that provides a binary named uglifyjs with a compatible interface.

Usage

cujs uses cosmiconfig to collect configuration before calling uglifyjs. That means, cujs will look for configuration (all the way up the directory tree until it hits the home directory) in the following places:

  • cujs property in package.json
  • .cujsrc file in JSON or YAML format
  • cujs.config.js file exporting a JS object

You can use camelCase variants of all options supported by uglifyjs in your configuration. In addition to that, you can also configure input files with the input key instead of passing them as arguments. Consider this example cujs.config.js:

module.exports = {
  input: ['foo.js', 'bar.js'],
  output: 'foo.min.js',
  compress: false,
  sourceMap: { url: "foo.min.js.map" },
}

This corresponds to the following uglifyjs arguments:

foo.js bar.js --output foo.min.js --no-compress --source-map url="foo.min.js.map"

Defaults

cujs applies the following defaults that differ from those of uglifyjs:

{
  mangle: true,
  compress: true,
  sourceMap: true,
  comments: /@preserve|@license|@cc_on|^!/i,
}

Furthermore, cujs tries to be smart about some things. For example, when sourcemaps are enabled, it infers sourceMap.url and looks for a input source map to use as sourceMap.content. However, if you explicitly set any of those keys, cujs won't touch them.

If in doubt, run as DEBUG=cujs cujs to see what's going on.

License

MIT © Raphael von der Grün