You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using babel-preset-react-app outside of create-react-app, and I'd like to be able to pass options down to the underlying Babel modules that are being used. For example, maybe something like:
...to pass a config object to babel-preset-latest. I understand that CRA has a general aversion to adding configuration, so I wanted to ask if this seemed like a reasonable addition (since the options won't actually be exposed to users of CRA)?
The text was updated successfully, but these errors were encountered:
I think it'd be better to do this for all of the included babel presets rather than just for babel-preset-env, so maybe it'd be better if #1415 placed its corresponding config underneath an env key to allow for other preset configurations, like this:
I would like to keep the Babel preset very strict right now to prevent combinatorial explosion of potential options (and thus issues reported). We will definitely support passing the browsers in the future, but this will be a part of #1249. Closing for now.
I'm using
babel-preset-react-app
outside ofcreate-react-app
, and I'd like to be able to pass options down to the underlying Babel modules that are being used. For example, maybe something like:...to pass a config object to
babel-preset-latest
. I understand that CRA has a general aversion to adding configuration, so I wanted to ask if this seemed like a reasonable addition (since the options won't actually be exposed to users of CRA)?The text was updated successfully, but these errors were encountered: