rollup-plugin-replace
Replace strings in files while bundling them.
Installation
npm install --save-dev rollup-plugin-replace
Usage
Generally, you need to ensure that rollup-plugin-replace goes before other things (like rollup-plugin-commonjs) in your plugins
array, so that those plugins can apply any optimisations such as dead code removal.
// rollup.config.js; // ... plugins: ;
Options
// a minimatch pattern, or array of patterns, of files that // should be processed by this plugin (if omitted, all files // are included by default)... include: 'config.js' // ...and those that shouldn't, if `include` is otherwise // too permissive exclude: 'node_modules/**' // To replace every occurrence of `<@foo@>` instead of every // occurrence of `foo`, supply delimiters delimiters: '<@' '@>' // All other options are treated as `string: replacement` // replacers... VERSION: '1.0.0' ENVIRONMENT: JSON // or `string: (id) => replacement` functions... `''` // ...unless you want to be careful about separating // values from other options, in which case you can: values: VERSION: '1.0.0' ENVIRONMENT: JSON
Word boundaries
By default, values will only match if they are surrounded by word boundaries — i.e. with options like this...
changed: 'replaced'
...and code like this...
console;console;
...the result will be this:
console;console;
If that's not what you want, specify empty strings as delimiters:
changed: 'replaced' delimiters: '' ''
License
MIT