-
Notifications
You must be signed in to change notification settings - Fork 177
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
Module not found: Default condition should be last one #840
Comments
I manually modified the package.json file inside the node_modules directory, and the changes appear to have resolved the issue with the following modification. Please investigate. Thanks.
|
Thanks for pointing this out. Fix will be released soon |
Hi Rhys,
Thank you for promptly addressing the issue and providing a fix. I will be testing the new build this morning and will keep you informed if any further issues arise.
Thanks again for your support.
Regards
Richard
… On 26 Sep 2024, at 6:01 am, Rhys Evans ***@***.***> wrote:
Thanks for pointing this out. Fix will be released soon
—
Reply to this email directly, view it on GitHub <#840 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADU7RTQM3USFNSMF7VFNAT3ZYMI75AVCNFSM6AAAAABOXPY6XWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZVGE2DCMRZHA>.
You are receiving this because you authored the thread.
|
Trying to use fetch-mock with Next.js and got the following error. I did some digging and found that Webpack expects the exports default condition in package.json to be last in this list, because it is a fallback for environments where no other specific condition applies.
`
Module not found: Default condition should be last one
The text was updated successfully, but these errors were encountered: