-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
ModuleNotFoundError: Could not find module in path: '<path/file>' relative to '<path/file>' #6172
Comments
Did you ever figure this out? I'm running into this now with one of my own modules. |
Hey Joe,
Would you be able to link us directly to the Sandbox in question?
…--- original message ---
On January 31, 2022, 5:28 PM GMT ***@***.*** wrote:
Did you ever figure this out? I'm running into this now with one of my own modules.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
--- end of original message ---
|
@CodeSandboxTeam super cool y'all have a Team GH account. Sorry for the noise. Turns out it was a user error. I was publishing the wrong files in my module 😅 |
These things happen , glad you found a fix!
…--- original message ---
On February 1, 2022, 4:34 PM GMT ***@***.*** wrote:
@CodeSandboxTeam super cool y'all have a Team GH account.
Sorry for the noise. Turns out it was a user error. I was publishing the wrong files in my module 😅
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you were mentioned.Message ID: ***@***.***>
--- end of original message ---
|
Hi, I have this same error in https://codesandbox.io/s/ancient-rgb-70b30 with the latest @primer/react version. This is specifically after a change that introduced subpath exports.
In the above error the relative path Here is the issue tracked in |
Thanks @pksjce - I definitely agree that it looks like an issue with the new resolver changes. I've flagged this on our end! |
Description of the problem
causes error:
How has this issue affected you? What are you trying to accomplish?
Prevents application from loading in codesandbox so that React Test Library support cannot help with an issue I have with testing.
Link to sandbox: link (optional)
The text was updated successfully, but these errors were encountered: