Incompatible with latest rollup-plugin-commonjs

[armpogart]

rollup-plugin-commonjs starting from version 8.4.0 is incompatible with rollup <= 0.56.0, and rollup-stream depends on rollup@0.42.0.

[lemmabit]

You can use this workaround until I update the dependency, assuming there haven't been any API changes that break it.

[armpogart]

@Permutatrix Thanks, but unfortunately I can't use that workaround as I'm using your plugin with rollup.config.js, see also my other issue #25. For the time being I will use the older version of rollup-plugin-commonjs.

I will also propose to move rollup from dependencies to peerDependencies as rollup-plugin-commonjs did to avoid similar issues in the future.
For the workaround to work and also to fix #25 issue, I would like to propose exposing second argument (object), where we can define configs manually and you would merge the latter with values specified in config file (which is first argument), so you will give a way to use config file and specify additional overriding configs, that way I will also be able to specify cache with config file.

Thanks.

[lemmabit]

@armpogart You can specify the rollup option in rollup.config.js, or at any rate I'm pretty sure you can. It probably won't work with the Rollup CLI anymore if you do, though. You could in principle have a separate rollup-stream.config.js that imports rollup.config.js, adds the rollup option to it, and re-exports it, but that would be pretty ugly.

Moving Rollup to peerDependencies has been suggested to me several times. I think peerDependencies are a bad idea. Dependency injection should be good enough for anyone IMO.

Your suggestion for this/#25 sounds good. I think I'll use it. Note that I've been thinking of making a v2 of this package with a different interface for a while now to make Rollup updates less of a hassle for everyone, but your change is a lot simpler, so I'll probably get it in for a v1.x.0 release.