transpile JS based on user agents
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.
- 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
- Supports CSS and JS
- Supports source maps, even inlined ones
var Ecstacy = require'ecstacy'
There are two builders.
Both inherit from
Ecstacy, defined below.
Delete the entire cache folder.
Ecstacy constructors have the following API:
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
"Builds" a version of the file according to
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
Get the absolute filename of a file.
Read a file by its name.
Buffer, so you need to
.toString() it yourself.
var ecstacy = Ecstacyjscode: 'var a = b;'ecstacybuilduseragentthenreturn ecstacyreaddatacode 'utf8'then
Create a read stream for a file and extension instead of buffering it. Useful when serving files to the client.