unenv

Once upon a time, one server was all needed to have a website

... And then SPAs¹ moved server code to browser

... And then SSR² moved browser code to server

... And then Workers³ moved browser/server code to workers

... Workers are neither NodeJS with process or Browser with window

... Yet expected to run code that had to work both of them

[1] Single Page Applications

[2] Server Side Rendering

[3] https://workers.cloudflare.com, https://deno.com/deploy

¯\_(ツ)_/¯

unenv is a collection of modules, polyfills, shims and presets that work perfectly with any Javascript environemnt including Browsers, Workers, NodeJS or pure JavaScript. Goal is that final bundle works consistent regardless of running context yet not adding excessive polyfills.

Install

Install un as devDependency:

yarn add --dev unenv
# or
npm i -D unenv

Usage: Generated env config

Using env utility and builtin presets (node and nodeless), unenv will provide an abstract config that can be used in building pipelines (rollup.js, webpack, etc)

import { env, node, nodeless } from 'unenv'

const { alias, inject, polyfill, external } = env(...presets)

Usage: As a runtime library

Alternatively, instead of using env generator, you can cherry-pick and combine runtime utilities individually in your source.

Runtime library

NodeJS

• fetch.node
• process
• IncomingMessage
• ServerResponse
• METHODS
• STATUS_CODES

net

• IncomingMessage
• ServerResponse
• METHODS
• STATUS_CODES

stream

• Socket

Mocking utilities

• Readable
• Writable

Shims

• proxy
• empty
• noop

polyfills

• consola
• mime-db
• mime
• debug

License

MIT