gulp plugin for Rollup ES6 module bundler
Note: This plugin is not appropriate for most use cases, as it requires every file expected to be imported by Rollup to be loaded into memory preemptively. rollup-stream is preferred for almost all purposes. If you want to transform/synthesize/alias/etc. the files Rollup processes, use Rollup plugins; if there's no Rollup plugin to do what you want, try the gulp-to-Rollup plugin adapter, rollup-plugin-gulp. If you really need to synthesize your files in gulp, go ahead and use gulp-rollup—that's what it's made for.
npm install --save-dev gulp-rollup
var gulp =rollup = ;gulp;
var gulp =rollup =sourcemaps = ;gulp;
If an array of strings is passed into
options.entry, a separate bundle will be rolled up from each entry point. They will be processed in parallel and output in no particular order. As usual, each bundle will have the same path as the associated entry file.
In addition, a Promise that resolves to a string or array of strings can be passed into
options.entry. This is to make it more convenient to use asynchronous methods to locate entry files.
In addition to the standard Rollup options, gulp-rollup supports
options.rollup, allowing you to use an older, newer, or custom version of Rollup by passing in the module like so:
options.allowRealFiles is set to true, gulp-rollup will break the gulp plugin guidelines just for you and allow Rollup to read files directly from the filesystem when a file with a matching name isn't found in the gulp stream. You could use this to weasel your way out of having to use rollup-stream, but that would make you a terrible person.
By default, gulp-rollup will mimic Rollup by adding a .js extension to imports if necessary. You can customize this behavior by setting
options.impliedExtensions to an array of extensions, like
['.js', '.es', '.jsx']. If
options.impliedExtensions is set to
false or an empty array, file extensions in imports will be treated as mandatory.