- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 141
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
ERR_PACKAGE_PATH_NOT_EXPORTED with dev server in v0.21.8 #1056
Comments
I'll look into it. Is it possible to reproduce this with modifying the template a little bit? |
Just to confirm, does reverting this line fix your issue? |
That does not seem to work. If I log the import, it's this with file:///path/to/waku/project/node_modules/waku/dist/minimal/client.js?v=466ecaf7 which causes an error: Error: Missing Root component With |
OK... instead of splitting on the
|
Thanks for looking into it. Splitting with |
This is reproduced when I'm trying #1012. |
Oops, that was my misunderstanding. So, I'm still interested in how to reproduce this error and adding a test. |
I think this is from running in a monorepo. Create a new folder. Add a package.json file with this:
Add a pnpm-workspace.yaml file with this:
In loadServerModuleMain, since my node_modules is outside the root of the waku project, it includes the full system root path in the request to load the module. That matches the With not in a monorepo, the |
I see. Maybe we should add a spec with a monorepo. #684 was closed as it's a bit stale, but something like that should be possible. Would you like to give a try? Or, maybe we look for someone who can help. |
I should be able to find a moment to create a monorepo e2e spec this week. 👍 |
I pushed #1079 to track creating a monorepo spec. I think we can go ahead and close this issue and track that effort there. |
Example error -
Package subpath './router/client.js?v=73b27883' is not defined by "exports"
This patch fixes it for me:
The text was updated successfully, but these errors were encountered: