
Product
Introducing GitHub Actions Scanning Support
Detect malware, unsafe data flows, and license issues in GitHub Actions with Socketβs new workflow scanning support.
@putout/engine-runner
Advanced tools
Run πPutout plugins.
npm i @putout/engine-runner
There is a couple plugin types available in πPutout:
All of them supports subset of JavaScript π¦PutoutScript described in @putout/compare.
They goes from simplest to hardest. Let's start from Declarator.
The simplest possible type of plugin, even simpler then Replacer:
module.exports.declare = () => ({
isString: `const isString = (a) => typeof a === 'string'`,
});
Based on @putout/operator-declare, helps to add declaration to any referenced Identifier.
Replacer converts code in declarative way. Simplest possible form of πPutout Plugin, no need to use fix. Just from and to parts
according to template variables syntax.
Simplest replace example:
module.exports.report = () => 'any message here';
module.exports.replace = () => ({
'const a = 1': 'const b = 1',
});
// optional
module.exports.filter = (path) => {
return true;
};
// optional
module.exports.match = () => ({
'const __a = 1': ({__a}) => {
return true;
},
});
// optional
module.exports.exclude = () => [
`const hello = 'world'`,
'ArrowFunctionExpression',
];
Simplest remove example:
module.exports.report = () => 'debugger should not be used';
module.exports.replace = () => ({
debugger: '',
});
// debugger; alert(); -> alert();
Templates:
module.exports.report = () => 'any message here';
module.exports.replace = () => ({
'var __a = 1': 'const __a = 1',
});
// var x = 1; -> const x = 1;
A couple variables example:
module.exports.report = () => 'any message here';
module.exports.replace = () => ({
'const __a = __b': 'const __b = __a',
});
// const hello = world; -> const world = hello;
You can pass a function as object value for more soficticated processing.
Remove node:
module.exports.report = () => 'any message here';
module.exports.replace = () => ({
'for (const __a of __b) __c': ({__a, __b, __c}, path) => {
// remove node
return '';
},
});
// for (a of b) {}; alert(); -> alert();
Update node:
module.exports.report = () => 'any message here';
module.exports.replace = () => ({
'for (const __a of __array) __c': ({__a, __array, __c}, path) => {
// update __array elements
path.node.right.elements = [];
return path;
},
});
// for (const a of [1, 2, 3]) {}; -> for (const a of []) {};
Update node using template variables:
module.exports.report = () => 'any message here';
module.exports.replace = () => ({
'for (const __a of __array) __c': ({__a, __array, __c}, path) => {
// update the whole node using template string
return 'for (const x of y) z';
},
});
// for (const item of array) {}; -> for (const x of y) z;
Includer is the most preferable format of a plugin, simplest to use (after Replacer):
module.exports.report = () => 'debugger statement should not be used';
module.exports.fix = (path) => {
path.remove();
};
module.exports.include = () => ['debugger'];
// optional
module.exports.exclude = () => {};
// optional
module.exports.filter = (path) => {
return true;
};
include and exclude returns an array of @babel/types, or code blocks:
const __ = 'hello';
Where __ can be any node. All this possible with help of @putout/compare. Templates format supported in traverse and find plugins as well.
Traverser gives you more power to filter and fix nodes you need.
module.exports.report = () => 'debugger statement should not be used';
module.exports.fix = (path, {options}) => {
path.remove();
};
module.exports.traverse = ({push}) => ({
'debugger'(path) {
push(path);
},
});
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:
Let's talk about each of them.
listStoreTo save things as a list without duplicates use listStore.
Let's suppose you have such code:
debugger;
const hello = '';
debugger;
const world = '';
Let's process it!
module.exports.traverse = ({listStore}) => ({
'debugger'(path) {
listStore(path);
},
Program: {
exit() {
console.log(listStore());
// returns
[{
type: 'DebuggerStatement',
}, {
type: 'DebuggerStatement',
}];
// for code
'debugger; debugger';
},
},
});
pathStoreWhen you want additional check that path not removed.
debugger;
const hello = '';
Let's process it!
module.exports.traverse = ({pathStore}) => ({
'debugger'(path) {
pathStore(path);
path.remove();
},
Program: {
exit() {
console.log(pathStore());
// returns
[];
},
},
});
storeWhen you need key-value use store:
module.exports.traverse = ({push, store}) => ({
'debugger'(path) {
store('hello', 'world');
push(path);
},
Program: {
exit() {
store();
// returns
['world'];
store.entries();
// returns
[['hello', 'world']];
store('hello');
// returns
'world';
},
},
});
upstoreWhen you need to update already saved values, use upstore:
module.exports.traverse = ({push, upstore}) => ({
TSTypeAliasDeclaration(path) {
if (path.parentPath.isExportNamedDeclaration())
return;
upstore(path.node.id.name, {
path,
});
},
ObjectProperty(path) {
const {value} = path.node;
const {name} = value;
store(name, {
used: true,
});
},
Program: {
exit() {
for (const {path, used} of upstore()) {
if (used)
continue;
push(path);
}
},
},
});
uplistWhen you need to update named arrays:
module.exports.traverse = ({uplist, push}) => ({
'const __object = __a.__b': (fullPath) => {
const {__a, __b} = getTemplateValues(fullPath, 'const __object = __a.__b');
const initPath = fullPath.get('declarations.0.init');
const {uid} = initPath.scope;
if (isIdentifier(__a) || isCallExpression(__a)) {
const {code} = generate(__a);
const id = `${uid}-${code}`;
return uplist(id, initPath);
}
},
'Program': {
exit: () => {
for (const items of uplist()) {
if (items.length < 2)
continue;
const index = items.length - 1;
const path = items[index];
push({
path,
items,
});
}
},
},
});
Scanner gives you all ability to work with files.
module.exports.report = () => 'Create file hello.txt';
module.exports.fix = (rootPath) => {
createFile(rootPath, 'hello.txt', 'hello world');
};
module.exports.scan = (rootPath, {push}) => {
const [filePath] = findFile(rootPath, 'hello.txt');
if (filePath)
return null;
push(rootPath);
};
You can also subscribe to progress events:
start;end;push;And one more: file if your plugin uses progress function:
export const report = () => 'Create file hello.txt';
export const fix = (rootPath) => {
createFile(rootPath, 'hello.txt', 'hello world');
};
export const scan = (rootPath, {progress}) => {
const [filePath] = findFile(rootPath, 'hello.txt');
if (filePath)
return null;
progress({
i: 0,
n: 1,
});
push(filePath);
};
Or better trackFile, which does the same, but also count progress:
export const report = () => 'Add file';
export const fix = (file) => {
writeFileContent(file, 'hello');
};
export const scan = (rootPath, {push, trackFile}) => {
for (const file of trackFile(rootPath, 'hello.txt')) {
push(file);
}
};
βοΈ When you use trackFile use progress() for testing
Finder gives you all the control over traversing, but it's the slowest format.
Because traversers not merged in contrast with other plugin formats.
module.exports.report = () => 'debugger statement should not be used';
module.exports.fix = (path) => {
path.remove();
};
module.exports.find = (ast, {push, traverse}) => {
traverse(ast, {
'debugger'(path) {
push(path);
},
});
};
const {runPlugins} = require('@putout/engine-runner');
const {parse} = require('@putout/engine-parser');
const plugins = [{
rule: 'remove-debugger',
msg: '', // optional
options: {}, // optional
plugin: {
include: () => ['debugger'],
fix: (path) => path.remove(),
report: () => `debugger should not be used`,
},
}];
const ast = parse('const m = "hi"; debugger');
const places = runPlugins({
ast,
shebang: false, // default
fix: false, // default
fixCount: 2, // default
plugins,
parser: 'babel', // default
});
To see logs, use:
DEBUG=putout:runner:*DEBUG=putout:runner:fixDEBUG=putout:runner:findDEBUG=putout:runner:templateDEBUG=putout:runner:replaceMIT
FAQs
Run πPutout plugins
The npm package @putout/engine-runner receives a total of 12,462 weekly downloads. As such, @putout/engine-runner popularity was classified as popular.
We found that @putout/engine-runner demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago.Β It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Product
Detect malware, unsafe data flows, and license issues in GitHub Actions with Socketβs new workflow scanning support.

Product
Add real-time Socket webhook events to your workflows to automatically receive pull request scan results and security alerts in real time.

Research
The Socket Threat Research Team uncovered malicious NuGet packages typosquatting the popular Nethereum project to steal wallet keys.