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

ecstacy

v2.0.1

Published

transpile JS based on user agents

Downloads

49

Readme

ecstacy

NPM version Build status Test coverage Dependency Status License Downloads Gittip

The perfect middleware between your static file server and the browser. Minifies, compresses, and caches files served to the client. If it's JS or CSS, it also transpiles unsupported features of the target browser. You may also use this in your build process to create browser-specific builds. It's traceur and myth on steroids.

The goal of this project is to create a frontend flow where:

  • JS, CSS, and HTML are written using the latest specifications (ES6, HTML imports, etc.)
  • The server resolves the dependencies tree
  • The server uses Ecstacy to transpile each file according to the target client and caches
  • The server HTTP2 pushes the files to the client

Combined with polyfills, you can use most of the latest features of browsers with relative ease.

There's no:

  • Build step to transpile your JS/CSS
  • Build step to concatenate your assets
  • Deploy step to create builds for every supported platform
  • Very little difference between the development and production environments

Features:

  • Supports CSS and JS
  • Supports source maps, even inlined ones
  • Caching

API

var Ecstacy = require('ecstacy')

Builders

There are two builders.

  • Ecstacy.js
  • Ecstacy.css

Both inherit from Ecstacy, defined below.

Ecstacy.clean()

Delete the entire cache folder.

Ecstacy

All Ecstacy constructors have the following API:

var ecstacy = new Ecstacy(options)

Create a new instance. Some options are:

  • name - the name of the file, specifically for source maps
  • code - source code
  • map - the source map, if any

ecstacy.build(agents).then( data => )

"Builds" a version of the file according to agents. agents is simply passed tp polyfills-db. data is an object with the following properties:

  • hash - the build hash
  • code - the filename for the code
  • map - the filename for the map

var filename = ecstacy.filename(name)

Get the absolute filename of a file.

ecstacy.read(name, encoding).then( buf => )

Read a file by its name. Returns a Buffer, so you need to .toString() it yourself.

var ecstacy = Ecstacy.js({
  code: 'var a = b;'
})
ecstacy.build(useragent).then(function (data) {
  return ecstacy.read(data.code, 'utf8')
}).then(function (js) {

})

ecstacy.stream(name)

Create a read stream for a file and extension instead of buffering it. Useful when serving files to the client.