Cache support for better performance about stream HOT 7 CLOSED

This is actually baked into Rollup. See: https://www.rollupjs.org/guide/en/#cache

The old rollup-stream wasn't actually doing anything with caching. See: https://github.com/Permutatrix/rollup-stream/blob/master/index.js

So you should already have this ability.

from stream.

Oh ok. I'm going to look into this tomorrow.

It would be good if this was clearly documented as part of the readme. This is incredibly important for fast build times.

from stream.

I'm not convinced that we need a readme section on this module. It's already stated clearly that all rollup options can be used, and are linked. Caching is pretty well documented on Rollup's site, and this module isn't limited to Gulp. Gulp is a popular streaming application, but definitely not the only one.

from stream.

The key thing that is confusing for Gulp users that is specific to this plugin is this question:

"How do I update the cached Rollup bundle using Gulp?"

This is something specific to @rollup/stream and if it isn't answered in the readme then the only way I can see for people to be able to answer that question is to look into the source code which is terrible UX.

This is something that seems silly to obscure from the user when 99% of Gulp users will need to make use of the cache option to optimise their watch task.

I'm working on a pull request right now to add documentation to the readme on how to optimise the Rollup gulp watch task.

from stream.

Pull request created: #3

from stream.

Closed by #3.

from stream.

Is there any way to detect that the next run of bundle.cache was changed comparing to previous one? I need to store the output of bundle, not the cache itself. I pass the previous cache to next run of rollup options and it looks like cache is used indeed, resulting in much faster builds. But still I do not know actually was there a single change or anything was not altered?

from stream.