Browser support

[Rich-Harris]

It would be useful to be able to run rollup in-browser, for the sake of custom builders (cc @mbostock) and interactive demos.

There are four external dependencies - path, sander, magic-string and acorn. acorn and magic-string both work in-browser (and magic-string and its only dependency use jsnext:main, so they be bundled with Rollup). The path functions can be replaced with internal helpers without too much difficulty.

sander is a little trickier, since it's a wrapper around fs. But if there were a neat way to exclude it from the build there'd be no problem - it's possible to supply a custom load function which returns the contents of the sought module (it just so happens that the default load uses sander to read from disk).

[Rich-Harris]

This is implemented in 0.11.0. Will try and get a demo site up soon

[donmccurdy]

Is there an example or demo? I'm wondering about doing this in the browser:

rollup.rollup({
  entry: '/foo/bar.js',
  plugins: [ ??? ]
}).then( bundle => {
  let { code, map } = bundle.generate({
    format: 'es6'   // amd, es6, iife, umd
  });
  console.log(code);
});

.. where /foo/bar.js is path relative to the current page, which might depend on other files.