Matthew Phillips

cc @phillipskevin

Breaking example can be reduced down to: ```js const flyd = require('flyd'); const filter = require('flyd/module/filter'); ```

This is kind of a weird one. Going to try and explain what is happening the best I can (more for people who might try and implement a fix): 1....

@kredati This is a good bug! Thanks for submitting, we'll try and get it on the next sprint.

I would prefer to turn off transpilation by default but I'm in the minority on this. Maybe in 2.0

You already have the ability to tune what is transpiled an what is not. Put your configuration into `steal.babelOptions`: https://stealjs.com/docs/StealJS.babel.html#plugins--presets

Running Steal code in Node is a general problem. Some times you want it to use the `browser` field, such as when you are doing a build, and then some...

This is a dupe of https://github.com/stealjs/steal/issues/1285. Will be fixed in the next patch release most likely.

We can discuss but this still sounds like the same issue. I'm not sure what feature you are requesting. But I don't think people should have to be aware of...

This warning is probably not visible now.