porsager/rollup-plugin-modify

Modify rollup output with find / replace dynamically

rollup-plugin-modify's Issues

Every replacement being in the same file is not a robust assumption

I've come across two separate issues with using the plugin where the built-in assumption that all the strings/regexes to replace would be in the same file fails;

      if (modifiers.every(x => !x[0].test(source)))
        return

1. I'm working on some source code that even for a development environment contains semi-secret variables (cloud service ids etc) that should not be commited. With a setup based on the BoilerWebApp repo, however, the dev.js script doesn't actually put everything into the same file, so the .every check fails.

2. For a production build, I have chosen to conditionally import/require separate files in the part of code that would be excluded (this is WIP for inlining bss stuff in the header), so while I can move the plugin location to such a place it actually replaces strings as expected, the bundling either fails or includes cruft that ideally should be tree-shaken away.

Relatedly, there's actually an inherent dependency on having this plugin in a specific place in the order of potential rollup-plugins that is not documented...

I realise that it's not necessarily an ideal situation, but perhaps optionally relaxing the same-file assumption might be an idea. Don't know if this is a situation with or what the possible solution for the issues might be with similar plugin implementations...