Open dominikzogg opened 1 year ago
As an information: 13.4.0 still of this issue
Hello @ijjk
Do you have an idea what is missing there to get any feedback?
Regards Dominik
We seem to have this issue as well. so if you us a "yarn link" with nextjs you will get this error. no clue on how to solve this.
@ebo-bpi cause i am using docker also on a local setup instead of symlinks i used docker mounts. Works but is a hack and breaks ide support cause your host system doesn't know about this references
@dominikzogg yep that could be a workaround also. I "fixed" it by importing the package by file path. just point it to the output dir of the remote package. only thing here is that you need to remove this from your package.json before pushing your code. Again also a workaround, but it won't stop me from moving at least. Would be nice if this could be solved anyway.
@ebo-bpi i would already appreciate any response from the developers.
Verify canary release
Provide environment information
Which area(s) of Next.js are affected? (leave empty if unsure)
>=13.3.2
Link to the code that reproduces this issue
https://github.com/dominikzogg/reproduction-app
To Reproduce
Use my repo with
master
branch (next:>=13.3.2
) and its broken, use theworking-version
branch13.3.1
and it works.Describe the Bug
When i upgrade next to >=13.3.2 it produces the following error:
It seems to work if its not symlinked (no issue on my build pipeline where files where copied to the
shared
folder withinproject
directory.I guess its related to: https://github.com/vercel/next.js/pull/48506
Expected Behavior
I expect that the code runs as it did until 13.3.1
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response