transform-arrow-functions being ignored for external packages? about babelify HOT 5 CLOSED

Yes, Browserify runs transforms on application code only by default. There are some pointers for solving this use case in the readme here https://github.com/babel/babelify/blob/master/README.md#why-arent-files-in-node_modules-being-transformed and in #268

from babelify.

As a follow up, it seems that babelify doesn't automatically load .babelrc anymore when you pass options as the 2nd argument to the transform like this:

browserify()
  .transform(babelify, {
    global: true
  });

As a work around, I used the find-babel-config package like this:

const findBabelConfig = require("find-babel-config");

const babelConfig = findBabelConfig.sync(__dirname);

browserify()
  .transform(babelify, {
    ...babelConfig.config,
    global: true
  });

cc: @goto-bus-stop

from babelify.

Ahh, global: true does what I want. Thanks for reading the readme for me!

from babelify.

One issue I ran into is that global is a babelify option, not a babel option, so global can't go in .babelrc. However, I found that I can do:

browserify()
.transform(babelify, {
  global: true
});

and have the rest of my babel config inside .babelrc

from babelify.

Yeah, this one's quite specific. It's a Browserify option: https://github.com/browserify/browserify#btransformtr-opts, opts.global is documented below the code sample.
Unlike other browserify transform options, it also doesn't work in the package.json browserify.transform key. It can only be used through the b.transform() API.

(Browserify's opinion is that package.json configuration should only apply to the package, not its dependencies or dependents.)

from babelify.