Issues with hooks from a symlinked directory, integrated via workspaces (npm) #49097
Comments
|
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. |
|
@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. |
|
@ebo-bpi i would already appreciate any response from the developers. |
|
This issue has been automatically marked as stale due to two years of inactivity. It will be closed in 7 days unless there’s further input. If you believe this issue is still relevant, please leave a comment or provide updated details. Thank you. |
Verify canary release
Provide environment information
Operating System: Platform: linux Arch: x64 Version: #1 SMP PREEMPT_DYNAMIC Mon May 1 00:55:28 UTC 2023 Binaries: Node: 18.16.0 npm: 9.6.5 Yarn: N/A pnpm: N/A Relevant packages: next: 13.3.1 eslint-config-next: N/A react: 18.2.0 react-dom: 18.2.0Which area(s) of Next.js are affected? (leave empty if unsure)
>=13.3.2Link to the code that reproduces this issue
https://github.com/dominikzogg/reproduction-app
To Reproduce
Use my repo with
masterbranch (next:>=13.3.2) and its broken, use theworking-versionbranch13.3.1and 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
sharedfolder withinprojectdirectory.I guess its related to: #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
The text was updated successfully, but these errors were encountered: