-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom babel config #26
Comments
If we move forward with this, we can document in the |
Note that this appears to work out of the box already if you simply configure plugins and transforms in your e.g. in package.json {
"name": "my-app",
…
"babel": {
"presets": [
"latest",
"react"
],
"plugins": [
"babel-plugin-istanbul",
"transform-runtime"
]
}
} This works because by default babel will merge any configurations it finds in parent directories. Users will need to set these up anyway if they're going to test code that runs outside However, I did not have any luck using |
@timoxley - great tip, did you figure out why mobx observers didn't fire? |
@timoxley It didn't work for my case. Looks like plugin added this way got lowest priority. Even lower then presets. Am I right? Is it how it's intended to work? I guess I need to fix my plugin to make it work regardless of priority. P.S. Hmm... It might be the source of problem with mobx |
@reflog NFI. |
@timoxley thanks a lot for that report. Very happy that it already partially works! |
As far as potential solutions, one could be that we consider the set of transformations performed by next the "next bundle", and you're able to override the entire configuration, specifying yourself where that next bundle falls. This is just a quick conjecture I just thought of, not sure if it's an actual solution. |
Perhaps directly take
babel
inpackage.json
, unlessnext.babel
is set.The text was updated successfully, but these errors were encountered: