
Research
SANDWORM_MODE: Shai-Hulud-Style npm Worm Hijacks CI Workflows and Poisons AI Toolchains
An emerging npm supply chain attack that infects repos, steals CI secrets, and targets developer AI toolchains for further compromise.
@rollup/plugin-replace
Advanced tools
🍣 A Rollup plugin which replaces targeted strings in files while bundling.
This plugin requires an LTS Node version (v14.0.0+) and Rollup v1.20.0+.
Using npm:
npm install @rollup/plugin-replace --save-dev
Create a rollup.config.js configuration file and import the plugin:
import replace from '@rollup/plugin-replace';
export default {
input: 'src/index.js',
output: {
dir: 'output',
format: 'cjs'
},
plugins: [
replace({
'process.env.NODE_ENV': JSON.stringify('production'),
__buildDate__: () => JSON.stringify(new Date()),
__buildVersion: 15
})
]
};
Then call rollup either via the CLI or the API.
The configuration above will replace every instance of process.env.NODE_ENV with "production" and __buildDate__ with the result of the given function in any file included in the build.
Note: Values must be either primitives (e.g. string, number) or function that returns a string. For complex values, use JSON.stringify. To replace a target with a value that will be evaluated as a string, set the value to a quoted string (e.g. "test") or use JSON.stringify to preprocess the target string safely.
Typically, @rollup/plugin-replace should be placed in plugins before other plugins so that they may apply optimizations, such as dead code removal.
In addition to the properties and values specified for replacement, users may also specify the options below.
delimitersType: Array[String, String]
Default: ['(?<![_$a-zA-Z0-9\\xA0-\\uFFFF])', '(?![_$a-zA-Z0-9\\xA0-\\uFFFF])(?!\\.)']
Specifies the boundaries around which strings will be replaced. By default, delimiters match JavaScript identifier boundaries and also prevent replacements of instances with nested access. See Word Boundaries below for more information.
For example, if you pass typeof window in values to-be-replaced, then you could expect the following scenarios:
typeof window will be replacedtypeof window.document will not be replaced due to the (?!\.) boundarytypeof windowSmth will not be replaced due to identifier boundariesDelimiters will be used to build a Regexp. To match special characters (any of .*+?^${}()|[]\), be sure to escape them.
objectGuardsType: Boolean
Default: false
When replacing dot-separated object properties like process.env.NODE_ENV, will also replace typeof process object guard
checks against the objects with the string "object".
For example:
replace({
values: {
'process.env.NODE_ENV': '"production"'
}
});
// Input
if (typeof process !== 'undefined' && process.env.NODE_ENV === 'production') {
console.log('production');
}
// Without `objectGuards`
if (typeof process !== 'undefined' && 'production' === 'production') {
console.log('production');
}
// With `objectGuards`
if ('object' !== 'undefined' && 'production' === 'production') {
console.log('production');
}
preventAssignmentType: Boolean
Default: false
Prevents replacing strings where they are followed by a single equals sign. For example, where the plugin is called as follows:
replace({
values: {
'process.env.DEBUG': 'false'
}
});
Observe the following code:
// Input
process.env.DEBUG = false;
if (process.env.DEBUG == true) {
//
}
// Without `preventAssignment`
false = false; // this throws an error because false cannot be assigned to
if (false == true) {
//
}
// With `preventAssignment`
process.env.DEBUG = false;
if (false == true) {
//
}
excludeType: String | Array[...String]
Default: null
A picomatch pattern, or array of patterns, which specifies the files in the build the plugin should ignore. By default no files are ignored.
includeType: String | Array[...String]
Default: null
A picomatch pattern, or array of patterns, which specifies the files in the build the plugin should operate on. By default all files are targeted.
sourceMap or sourcemapType: Boolean
Default: false
Enables generating sourcemaps for the bundled code. For example, where the plugin is called as follows:
replace({
sourcemap: true
});
valuesType: { [key: String]: Replacement }, where Replacement is either a string or a function that returns a string.
Default: {}
To avoid mixing replacement strings with the other options, you can specify replacements in the values option. For example, the following signature:
replace({
include: ['src/**/*.js'],
changed: 'replaced'
});
Can be replaced with:
replace({
include: ['src/**/*.js'],
values: {
changed: 'replaced'
}
});
By default, values will only match if they are surrounded by word boundaries that respect JavaScript's rules for valid identifiers (including $ and _ as valid identifier characters).
Consider the following options and build file:
module.exports = {
...
plugins: [replace({ changed: 'replaced' })]
};
// file.js
console.log('changed');
console.log('unchanged');
The result would be:
// file.js
console.log('replaced');
console.log('unchanged');
To ignore word boundaries and replace every instance of the string, wherever it may be, specify empty strings as delimiters:
export default {
...
plugins: [
replace({
changed: 'replaced',
delimiters: ['', '']
})
]
};
This Babel plugin allows you to replace specified nodes in your Babel AST with arbitrary values, similar to how @rollup/plugin-replace works. The difference lies in the approach: babel-plugin-transform-define operates on the AST level during the transpilation step, rather than during the bundling process.
FAQs
Replace strings in files while bundling
The npm package @rollup/plugin-replace receives a total of 3,304,817 weekly downloads. As such, @rollup/plugin-replace popularity was classified as popular.
We found that @rollup/plugin-replace demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 4 open source maintainers 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.

Research
An emerging npm supply chain attack that infects repos, steals CI secrets, and targets developer AI toolchains for further compromise.

Company News
Socket is proud to join the OpenJS Foundation as a Silver Member, deepening our commitment to the long-term health and security of the JavaScript ecosystem.

Security News
npm now links to Socket's security analysis on every package page. Here's what you'll find when you click through.