Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Babel can not resolve plugins in parent folder with yarn workspaces #6342
See yarnpkg/yarn#4503 for the issue filed against yarn, but there is discussion there that yarn is not responsible so I'm opening one here as well.
In short, yarn workspaces can cause babel-plugins to be installed outside of the project root so babel is unable to resolve them properly. It's arguable that babel should look above the project root in other
Hey @zyklus! We really appreciate you taking the time to report an issue. The collaborators
Hi @zyklus! A maintainer of the project has notified me that you're missing
Please understand that we receive a high volume of issues, and there are only a limited number
Please make sure you have the following information documented in this ticket:
Please provide either a link to the problem via the
@loganfsmyth I think that the issue that I just found can be related.
I have a monorepo project using yarn workspaces with the following structure:
The app package is the main entry of the whole app and you fire up that with
The main page of the package
When running next, an error arise related with transpilation.
So, as far as I understand:
Is there any solution (even if it's hacky) for something like this? or is this the expected behavior of babel-loader and is more a problem for nextjs guys?
@matiasfh my nextjs project has a different structure, but it also faces an issue with
for now I am defining
I wonder, though, who should we report this to. Nextjs, babel or yarn?