From 8f0e70bad4d85030bbc644c762bdc38aedeaac32 Mon Sep 17 00:00:00 2001 From: Aaron Ang Date: Tue, 7 Mar 2017 20:17:38 -0800 Subject: [PATCH] Change CONTRIBUTING.md to use absolute paths [skip ci] --- experimental/babel-preset-env/CONTRIBUTING.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/experimental/babel-preset-env/CONTRIBUTING.md b/experimental/babel-preset-env/CONTRIBUTING.md index fad3b24823..e3c0b46aef 100644 --- a/experimental/babel-preset-env/CONTRIBUTING.md +++ b/experimental/babel-preset-env/CONTRIBUTING.md @@ -2,7 +2,7 @@ ### Adding a new plugin to support (when approved in the next ECMAScript version) -#### Update [`pluginFeatures.js`](/data/plugin-features.js) +#### Update [`pluginFeatures.js`](https://github.com/babel/babel-preset-env/blob/master/data/plugin-features.js) Example: @@ -12,7 +12,7 @@ Find the relevant entries on [compat-table](https://kangax.github.io/compat-tabl `exponentiation (**) operator` -Find the corresponding babel plugin: +Find the corresponding babel plugin: `transform-exponentiation-operator` @@ -26,8 +26,8 @@ Add add them in this structure: ], }, ``` - -#### Update [`plugins.json`](/data/plugins.json) + +#### Update [`plugins.json`](https://github.com/babel/babel-preset-env/blob/master/data/plugins.json) Until `compat-table` is a standalone npm module for data we are using the git url @@ -45,11 +45,11 @@ please read our [documentation on writing tests](https://github.com/babel/babel/ #### Testing the `debug` option -Testing debug output to `stdout` is similar. Under the `test/debug-fixtures`, +Testing debug output to `stdout` is similar. Under the `test/debug-fixtures`, create a folder with a descriptive name of your test, and add the following: -* Add a `options.json` file (just as the other tests, this is essentially a +* Add a `options.json` file (just as the other tests, this is essentially a `.babelrc`) with the desired test configuration (required) -* Add a `stdout.txt` file with the expected debug output. For added -convenience, if there is no `stdout.txt` present, the test runner will +* Add a `stdout.txt` file with the expected debug output. For added +convenience, if there is no `stdout.txt` present, the test runner will generate one for you.