-
Notifications
You must be signed in to change notification settings - Fork 203
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
cwd: 'babelrc' doesn't find .babelrc.js #311
Comments
find-babel-config supports .babelrc.js though: https://github.com/tleunen/find-babel-config/tree/master/test/data/babelrcjs |
Yeah... But we'll have to rework that option with Babel 7 anyway I believe... So I wonder how useful is the babelrc custom cwd that we have instead of always using the root project... Defaulting on the root project, except if you provide a custom cwd. No more custom magic values. |
@fatfisz That's odd - I was getting absolute paths (as if it weren't finding the cwd) when I had a @tleunen In the case of a monorepo, with Babel 7's |
What do you mean exactly. If you have one babel.config.js in each "package" in the monorepo. It will be ok. (But then I agree that the project root won't be the same). But anyway, I think using the new core function |
It looks like https://babeljs.io/docs/en/next/babelconfigjs Unless you opt into them using the |
I was having trouble getting babel to export aliased modules -- they were always transpiling with absolute paths instead of relative ones. I had been configuring babel with a
.babelrc.js
file instead of.babelrc
--- when I renamed it, things started working as expected.It would be ideal if
.babelrc.js
files were supported!I'm happy to put together a PR for this. It looks like
find-babel-config
isn't very active, it might make sense to handle this from within this module.The text was updated successfully, but these errors were encountered: