-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
fix(dev): get deps from ESM packages without main #7272
Conversation
🦋 Changeset detectedLatest commit: 31dd297 The changes in this PR will be included in the next version bump. This PR includes changesets to release 16 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
While attempting to upgrade Remix Utils to the latest version, I encountered the following error: ``` Error [ERR_REQUIRE_ESM]: require() of ES Module ... Instead change the require of promise.js ``` Diving deeper I realized that the error was due to my oversight. I had overlooked the warning to _add each individual utility_ to the serverDependenciesToBundle configuration. Subsequently, I also noticed that a related pull request ([PR](remix-run/remix#7272)) had been merged into Remix version [2.0.1](https://github.com/remix-run/remix/releases/tag/remix%402.0.1) but had not completely resolved the issue. By adding `/^remix-utils.*/,` in lieu of `"remix-utils"` and every individual util to `serverDependenciesToBundle`, it stops showing the error.
This PR adds some extra logic to
getDependenciesToBundle
to handle the case where an ESM package doesn't provide an export for"./"
but provides one for"./package.json"
.Closes #3106