Non-default exports break rollup.config.js

[swansontec]

• Rollup Version: 1.0.0
• Operating System (or Browser): OSX
• Node Version: v11.4.0

How Do We Reproduce?

Create a rollup.config.js file with an extra non-default export:

export default {
  input: './index.js',
  output: { file: './out.js', format: 'cjs' }
}

export const redHerring = 1

Expected Behavior

This should still be a valid config file, since the non-default redHerring export shouldn't change anything.

Actual Behavior

Rollup fails with some warnings followed by an error:

(!) Mixing named and default exports
Consumers of your bundle will have to use bundle['default'] to access the default export, which may not be what you want. Use `output.exports: 'named'` to disable this warning
(!) You have passed an unrecognized option
Unknown input option: default, redHerring. Allowed options: acorn, acornInjectPlugins, cache, chunkGroupingSize, context, experimentalCacheExpiry, experimentalOptimizeChunks, experimentalTopLevelAwait, external, inlineDynamicImports, input, manualChunks, moduleContext, onwarn, perf, plugins, preserveModules, preserveSymlinks, shimMissingExports, treeshake, watch
undefined → stdout...
[!] Error: You must supply options.input to rollup

Pull request #2673 provides a solution to this problem.

[lukastaegert]

Resolved via #2673