control the order of transforms

use case:

var aliasify = require('aliasify');
var myTransform = require('my-custom-transform');
...
b.transform(aliasify);
b.transform(myTransform);

I expect that files being compiled go through aliasify before running through myTransform. I tried switching the order of lines 4 and 5, and i get the same result, which is myTransform is being applied first.

Is there a way to control this? if not, would you consider implementing it? Thanks

[kentmw]

I modified jsFilesOnly in my downloaded node_modules/aliasify/aliasify.js, and it worked. At least, it worked in my case. I’ll try out the appliedTo option, and move this conversation over to the aliasify project. Thank you so much for your help!

EDIT: it works to use appliesTo and is most likely the preferred method.

  "aliasify": {
    "aliases": {
      "app": "./app",
    },
    "appliesTo": {"includeExtensions": [".js", ".hbs"]}
  }

[jmm]

Hi @kentmw, transforms are stream based so inherently async, but of course they run in sequence on a given file. Maybe it has something to do with this: options.jsFilesOnly. Anyway, I’m closing this issue because no one has provided a repro. I suspect your problem has to do with how those two transforms interact rather than something fundamental about how Browserify transforms work. Stackoverflow is one place you can try for help. If you’re able to isolate a bug in Browserify’s transform handling, please open a new issue with a minimal repro. If you need help getting started see miniminirepro/browserify. Thanks!