@putout/engine-runner 14.0.2 → 14.1.1

package/README.md

@@ -15,10 +15,10 @@ npm i @putout/engine-runner
 
 There is a couple plugin types supported by 🐊**Putout**:
 
-- ✅[`Replacer`](#replacer)
-- ✅[`Includer`](#includer)
-- ✅[`Traverser`](#traverser)
-- ✅[`Finder`](#finder)
+- ✅ [**Replacer**](#replacer)
+- ✅ [**Includer**](#includer)
+- ✅ [**Traverser**](#traverser)
+- ✅ [**Finder**](#finder)
 
 All of them supports subset of **JavaScript** 🦎[**PutoutScript**](https://github.com/coderaiser/putout/blob/master/docs/putout-script.md#-putoutscript) described in [`@putout/compare`](https://github.com/coderaiser/putout/tree/master/packages/compare#readme).
 
@@ -145,7 +145,7 @@ module.exports.replace = () => ({
 
 ### Includer
 
-`includer` is the most preferable format of a plugin, simplest to use (after `replacer`)
+**Includer** is the most preferable format of a plugin, simplest to use (after `Replacer`):
 
 ```js
 module.exports.report = () => 'debugger statement should not be used';
@@ -178,7 +178,7 @@ Where `__` can be any node. All this possible with help of [@putout/compare](htt
 
 ### Traverser
 
-`Traverse plugins` gives you more power to `filter` and `fix` nodes you need.
+**Traverser** gives you more power to `filter` and `fix` nodes you need.
 
 ```js
 module.exports.report = () => 'debugger statement should not be used';
@@ -196,7 +196,7 @@ module.exports.traverse = ({push}) => ({
 
 ### Finder
 
-`Find plugins` gives you all the control over traversing, but it's the slowest format.
+**Finder** gives you all the control over traversing, but it's the slowest format.
 Because `traversers` not merged in contrast with other plugin formats.
 
 ```js
@@ -219,7 +219,7 @@ module.exports.find = (ast, {push, traverse}) => {
 
 ```js
 const {runPlugins} = require('@putout/engine-runner');
-const {parse} = require('@putout/engin-parser');
+const {parse} = require('@putout/engine-parser');
 
 const plugins = [{
     rule: 'remove-debugger',
@@ -248,11 +248,11 @@ const places = runPlugins({
 Stores is preferred way of keeping 🐊**Putout** data, `traverse` init function called only once, and any other way
 of handling variables will most likely will lead to bugs. There is a couple store types:
 
-- ✅`listStore`;
-- ✅`pathStore`;
-- ✅`store`;
-- ✅`upstore`;
-- ✅`uplist`;
+- ✅ [`listStore`](#liststore);
+- ✅ [`pathStore`](#pathstore);
+- ✅ [`store`](#store);
+- ✅ [`upstore`](#upstore);
+- ✅ [`uplist`](#uplist);
 
 Let's talk about each of them.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@putout/engine-runner",
-  "version": "14.0.2",
+  "version": "14.1.1",
   "type": "commonjs",
   "author": "coderaiser <mnemonic.enemy@gmail.com> (https://github.com/coderaiser)",
   "description": "Run 🐊Putout plugins",
@@ -48,7 +48,7 @@
     "eslint-plugin-n": "^15.2.4",
     "eslint-plugin-putout": "^16.0.0",
     "just-camel-case": "^4.0.2",
-    "lerna": "^5.0.0",
+    "lerna": "^6.0.1",
     "madrun": "^9.0.0",
     "mock-require": "^3.0.3",
     "montag": "^1.0.0",