Stream Non-Entry Files

I’m trying to also stream files that the entry file requires is this possible? I have been looking for a while and haven’t found innate to browserify or a plugin.

Simplified Example:

const str = require('string-to-stream');
const browserify = require('browserify');

const entry = "const func = require('./func.js')";
const func = "module.exports = function() {return 'func'}";

browserify(str(entry), {basedir: __dirname})
  // somehow map './func.js' to func string

[mattdesl]

I am doing some similar things in my tools, generating source on the fly in response to certain require statements. If you are OK with requiring a module name like 'foo-bar' rather than relative path, you can do this:

const fromStr = require('from2-string');
const browserify = require('browserify');

const entry = `module.exports = require('foo-bar');`;
const other = `module.exports = "foobar";`;

const b = browserify(fromStr(entry), {
  basedir: __dirname
});

b.exclude('foo-bar');
b.require(fromStr(other), {
  // Make up a file name for the stream
  // If the file name is within node_modules, then
  // it will get skipped by non-global transforms
  file: 'foo-bar.js',
  expose: 'foo-bar'
});

b.bundle((err, src) => {
  if (err) throw err;
  console.log(src.toString());
});

If you need relative file names like ./foo-bar.js, you may have to dive into plugins, potentially doing something like altering the .source property as rows come through the pipeline, if the id matches the file you are trying to modify.

NOTE: These things can cause issues with watchify since there is no file on disk to invalidate the cache; so you can’t really have a dynamic stream that changes over the course of development. At some point I hope watchify or browserify API will introduce some method of invalidating a resource by file ID or something, to fix this pitfall.

[BebeSparkelSparkel]

Repo for plugin require_stringify