rollup 0.52.1 cannot parse tagged template strings in 'rollup.config.js'

[feross]

It looks like rollup 0.52.1 started parsing the rollup.config.js file with buble (in this PR #1759). This breaks my config which is using a tagged template string. Apparently buble does not support these.

[!] (buble plugin) CompileError: Tagged template strings are not supported. Use `transforms: { templateString: false }` to skip transformation and disable this error, or `transforms: { dangerousTaggedTemplateString: true }` if you know what you're doing (40:10)
rollup.config.js (40:10)
36 :       externalHelpers: true
37 :     }),
38 :     commonjs()
39 :   ],
40 :   banner: stripIndent`
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

The PR where this was introduced is #1759 which was adding support for object rest/spread. Is it possible to support object rest/spread without breaking other features already supported by modern Node runtimes? Or am I doing something wrong?

[lukastaegert]

As both this issue and #1873 could be easily solved by reverting #1759 I guess that is the way we should go. Maybe as part of the code-splitting release if I find the time. Otherwise, a reverting PR is certainly welcome.

Sorry @haraldrudell who made this PR in the first place. But after all the discussion, my feeling is that going back to what the host system supports is the best and purest solution. You can always just create a simple npm script like

"build": "npx babel rollup.config.js --out-file rollup.config.transpiled.js && rollup -c rollup.config.transpiled.js"

to enable unsupported syntax in the config.

[lukastaegert]

Should be fixed now

[feross]

👏