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
{{ message }}
This repository has been archived by the owner on Apr 9, 2020. It is now read-only.
I'm creating a set of reusable react components, and having a .babelrc file is problematic, so I would like to avoid having one if possible. I cannot figure out how to translate the option objects for transforms into a cli-friendly format. Can this be used without a .babelrc, and if so, how?
The text was updated successfully, but these errors were encountered:
I certainly would like to use a .babelrc, except that I've found that if a library has one, the consuming app will try to use it (see this issue). In my development model, I want to use npm link and work concurrently in the library and consuming project rather than frequently publishing to npm, so I can't just add it to my .npmignore. Or, I may move the whole library into my consuming app, but it will still need a unique babel configuration. If you have suggestions of how I could continue using a .babelrc, I'd love to know how.
I'm creating a set of reusable react components, and having a
.babelrc
file is problematic, so I would like to avoid having one if possible. I cannot figure out how to translate the option objects fortransforms
into a cli-friendly format. Can this be used without a.babelrc
, and if so, how?The text was updated successfully, but these errors were encountered: