# future-node

> babel-node meets browserify-ish transforms

Latest version **0.0.2** (published 2016-05-22) · MIT license · 0 weekly downloads

## Install

```sh
npm install future-node
pnpm add future-node
yarn add future-node
bun add future-node
```

Provides the command `future-node`.

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support; pre 1.0.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 0.0.2 |
| Published | 2016-05-22 |
| First published | 2015-12-16 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 16 |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 0 |
| Author | Jake Rosoman |
| Maintainers | jkroso |
| Keywords | require hook, babel, transpile, node |

## Links

- npm: https://www.npmjs.com/package/future-node
- Repository: https://github.com/jkroso/future-node
- Homepage: https://github.com/jkroso/future-node#readme
- Issues: https://github.com/jkroso/future-node/issues
- npm.io page: https://npm.io/package/future-node

## Dependencies (16)

- [jsx-to-js](https://npm.io/package/jsx-to-js.md) 1
- [babel-core](https://npm.io/package/babel-core.md) 6
- [glob-to-regexp](https://npm.io/package/glob-to-regexp.md) 0
- [resolve-module](https://npm.io/package/resolve-module.md) 0
- [source-map-support](https://npm.io/package/source-map-support.md) 0
- [babel-plugin-syntax-jsx](https://npm.io/package/babel-plugin-syntax-jsx.md) 6
- [@jkroso/babel-plugin-runtime](https://npm.io/package/@jkroso/babel-plugin-runtime.md) 1
- [babel-plugin-transform-function-bind](https://npm.io/package/babel-plugin-transform-function-bind.md) 6
- [babel-plugin-transform-class-properties](https://npm.io/package/babel-plugin-transform-class-properties.md) 6
- [babel-plugin-transform-es2015-parameters](https://npm.io/package/babel-plugin-transform-es2015-parameters.md) 6
- [babel-plugin-transform-async-to-generator](https://npm.io/package/babel-plugin-transform-async-to-generator.md) 6
- [babel-plugin-transform-object-rest-spread](https://npm.io/package/babel-plugin-transform-object-rest-spread.md) 6
- [babel-plugin-transform-es2015-destructuring](https://npm.io/package/babel-plugin-transform-es2015-destructuring.md) 6
- [babel-plugin-transform-es2015-unicode-regex](https://npm.io/package/babel-plugin-transform-es2015-unicode-regex.md) 6
- [babel-plugin-transform-es2015-modules-commonjs](https://npm.io/package/babel-plugin-transform-es2015-modules-commonjs.md) 6
- [babel-plugin-transform-exponentiation-operator](https://npm.io/package/babel-plugin-transform-exponentiation-operator.md) 6

## Alternatives

- [@openai/codex-sdk](https://npm.io/package/@openai/codex-sdk.md) — 731.4K weekly downloads
- [babel-plugin-transform-react-jsx](https://npm.io/package/babel-plugin-transform-react-jsx.md) — 565.0K weekly downloads
- [babel-helper-remove-or-void](https://npm.io/package/babel-helper-remove-or-void.md) — 508.5K weekly downloads
- [@pnpm/store-controller-types](https://npm.io/package/@pnpm/store-controller-types.md) — 186.9K weekly downloads
- [react-native-signature-canvas](https://npm.io/package/react-native-signature-canvas.md) — 155.6K weekly downloads

## Recent versions

- 0.0.2 (latest) — 2016-05-22
- 0.0.1 — 2016-01-13
- 0.0.0 — 2015-12-16

## README

# future-node

Actually though it doesn't _give_ you future syntax automatically, it just enables modules to specify their transpilers. It does this by replacing node's built in system of extension hooks with a better system inspired by browserify. So a more accurate name for this project would be transpiler-friendly-node since its not really opinionated about your transpiler. It does come bundled with a ES2016 transpiler though for convenience since this will be its most common usage.

## Installation

`npm install future-node`

then in your app:

```js
require('future-node')
```

Or install it globally an run like

```sh
future-node my-app
```

## Specifying transpilers

Transpilers are specified in your `package.json`

```json
{
  "dependencies": {
    "some-module-that-exports-a-function": "1",
    "a-lisp-to-js-thing": "1"
  },
  "transpile": [
    ["*.js", "some-module-that-exports-a-function", {"options": true}],
    ["*.lisp", "a-lisp-to-js-thing"]
  ]
}
```

Hopefully it explains itself. To use the built in ES2016 transpiler

```json
{
  "transpile": [
    ["*.js", "!sourcegraph/babel->js", {"stage": 0}]
  ]
}
```

Weird I know. It's just so as to be compatable with my browser build bundler. You can safely ignore it if you like.

---
_Source: https://npm.io/package/future-node · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._