Tommy
Tommy
@ChiuMungZitAlexander This is interesting. Without using `~components` in your source code, it means you're using the "root" configuration to resolve your paths, which makes sense since you have `./src` as...
If anyone is willing to setup a testcase using the react-native bundler, this might also help us catching these issues specific to react native
Hi Bill, Indeed. This is a very strange behavior. I've never experienced this kind of things myself. And without a real context, it is hard to see and find the...
If you're able to create a new project reproducing your issue, with the same babelrc example that you provided, it will be very helpful. When I'm saying reducing the scope,...
Yeah, it seems tricky to fix this issue with react-native. I don't exactly know how it works, or how the cache works, but I doubt we can actually do anything...
@fatfisz - Would you like to jump on this? :) @Francesco-Lanciana First of all, thank you for the PR to try to add this functionality. To answer your question about...
What do you mean exactly? Could you give an example?
Yeah... But we'll have to rework that option with Babel 7 anyway I believe... `babel.config.js` works differently than the other filenames (see https://babeljs.io/docs/en/next/babelconfigjs). So I wonder how useful is the...
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...
Do you have a babelrc file in `./node_modules/project-a`?