brfs breaks source maps

[mikolalysenko]

I love brfs, but this issue is right now my number one annoyance. To replicate this, take any multifile bundle and add an fs.readSync with brfs. Open up the result in chrome, and you get a single giant blob.

Any ideas on what could be done to fix this situation?

[revolunet]

any news on this ? can brfs support source maps ?

[mattdesl]

I am not sure this issue will ever be solved with the current iteration of static-module – it will take a refactor (which might be worthwhile since that module has gotten pretty hairy) or building on top another source transformer altogether.

I experimented with the latter here:
https://github.com/Jam3/brfs-babel

It supports source maps and some (but not all) of brfs use cases. Since it builds on babel, things like removing nodes are trivial to implement. However, babel does not support async transformations, so it will probably never replace static-module.

[goto-bus-stop]

f8c924a

📦 1.5.0

[boris-ulyanov]

Update 1.4.4 to 1.5.0 breaks sourcemap for my case:

• node 8.9.4
• budo 11.2.0 / browserify 16.1.0

[blackgate]

Still breaks the sourcemaps here too.

[goto-bus-stop]

In what way? Can you share an example?

[blackgate]

Sure:

const fs = require("fs");
const browserify = require("browserify");
browserify("./script.js", { debug: true })
  .transform("babelify", {presets: ["env"], sourceMaps: true})
  .transform("brfs")
  .bundle()
  .pipe(fs.createWriteStream("bundle.js"));

With the .transform("brfs") line, the sourcemap contains the transpiled source instead of the original.

[goto-bus-stop]

Thanks, moving to #86!