-
Notifications
You must be signed in to change notification settings - Fork 27.4k
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
Inline next-transpile-modules #35150
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
An alternative would be to always transpile paths that do not contain This is always valid in yarn, npm and pnpm workspaces, the local packages real paths (the path linked by symlinks) will always be in a directory out of |
@remorses that's already covered by I agree that you shouldn't have to configure what packages exist in a workspaces setup, basically expanding |
This comment was marked as off-topic.
This comment was marked as off-topic.
@jaredpalmer The |
@timneutkens shared the details here. Sorry for that I had missed it. |
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Describe the feature you'd like to request
As a monorepo user that leverages yarn, npm, pnpm workspaces, Next.js requires an external plugin that degrades build performance (
next-transpile-modules
) because of symlink quirks.Describe the solution you'd like
Inline/enable a similar feature to
next-transpile-modules
directly into Next.js.For example, imagine there is a package called
@acme/ui
in a workspaces monorepo.Describe alternatives you've considered
n/a
The text was updated successfully, but these errors were encountered: