History

Make the filename option, as exposed to the plugins, consistently relative to the working directory (#7956 )

| Q                        | A <!--(Can use an emoji 👍) -->
| ------------------------ | ---
| Fixed Issues?            | 
| Patch: Bug Fix?          | Y
| Major: Breaking Change?  | N
| Minor: New Feature?      |
| Tests Added + Pass?      | Yes
| Documentation PR         | <!-- If so, add `[skip ci]` to your commit message to skip CI -->
| Any Dependency Changes?  |
| License                  | MIT

Currently the `opts.filename` value exposed to plugins is just whatever the user passed. While it _could_ be relative to the working directory, if Babel was passed an absolute URL, it'll be absolute.

This PR explicitly ensures the filename is a relative path based on the working directory. This also exposes an officially endorsed API for reading the working directory path.

2018-05-21 17:10:57 -07:00

bin

Scoped: updated numerous docs with scoped packages change [skip ci]

2017-10-16 22:49:57 -04:00

src

Refactor CLI to use promises/async fns.

2018-05-14 23:07:50 -07:00

test

Make the filename option, as exposed to the plugins, consistently relative to the working directory (#7956 )

2018-05-21 17:10:57 -07:00

.npmignore

Misc (#5545 )

2017-03-25 21:46:16 -04:00

index.js

Scoped: updated more docs with scoped packages change [skip ci]

2017-10-16 22:49:57 -04:00

package.json

v7.0.0-beta.47

2018-05-14 17:15:44 -07:00

README.md

@babel/cli: removed babel-node mention in README.md [skip ci] (#6829 )

2017-11-16 18:04:10 +01:00

README.md

@babel/cli

Babel command line.

In addition, various entry point scripts live in the top-level package at @babel/cli/bin.

There is a shell-executable utility script, babel-external-helpers.js, and the main Babel cli script, babel.js.

Install

npm install --save-dev @babel/core @babel/cli

Usage

babel script.js

For more in depth documentation see: http://babeljs.io/docs/usage/cli/