fix(plug-in): apply transforms and plugins on every rebuild

[bendrucker]

So with browserify 7.0.1 manually resetting the bundle requires the transforms to be reapplied. Pretty sure the offending change is:

browserify/browserify@7.0.0...7.0.1#diff-168726dbe96b3ce427e7fedce31bb0bcL274

Not sure whether resetting is still necessary @nikku

[nikku]

Browserifyyyyyyy ....

[bendrucker]

Lol. Possible a good time to change the prebundle behavior and move to configure and prebundle.

[nikku]

Before we merge this and perform a major update we should look into #52, too.

[bendrucker]

Yeah definitely. The intent here was just to highlight the required change. Will probably ended up making more sense to cherry pick the commit onto a different branch with other changes.

[xdissent]

Oh hi didn't see this... I just added a PR that fixes this problem. Browserify 7.0.1 had a weird bug that made the transform handling even weirder than 7.0.0 was supposed to make it. It's fixed in 7.0.2, but there's still a little funny business you have to pull to get it to behave the way we need it to: #68

[nikku]

If both PRs solve the same issue, I'd go with this one. Browserify internals seem to change rather frequently so it might be safer to rely on the public API.

[nikku]

I'll look into all the recent changes soon.

[xdissent]

I feel ya, but I think re-instantiating a plugin/transform multiple times on the same bundler instance may cause more issues downstream. There's already a subtle difference in the way transforms and plugins are initialized depending on whether they're passed as options or added after the constructor is called (but the other PR makes up for this) so I'd tread lightly. The whole 7.0.0 thing really made stuff confusing, so yeah, no rush on any of this obviously.

[nikku]

Using #68 as a solution.

@xdissent You are right about the reinstantiation problem. I don't want to get into that at all.