-
Notifications
You must be signed in to change notification settings - Fork 208
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 #486
Comments
Sure enough, from the NodeJS docs it says:
I broke that with #484 sorry about that! 🤦 Give me a few minutes and I'll make a PR to re-order them. |
Thanks for reporting this @micheledilernia-kanpla! |
@angus-c and @saibotsivad It's working fine! Thanks😁 |
Hi😁
I'm having some troubles building my Next.js project. The terminal keeps throwing this error:
Module not found: Default condition should be the last one
.Searching around I found this link that explains why it happens: Module not found: Default condition should be the last one.
Basically, the error tells that the default entry should be the last entry in the package.json. And concurrently with the rule
enhanced-resolve
of webpack the error is thrown.Would it be possible to move the
default
entry to the last position?Like so:
The text was updated successfully, but these errors were encountered: