-
Notifications
You must be signed in to change notification settings - Fork 0
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
An in-range update of esm is breaking the build 🚨 #41
Comments
After pinning to 3.0.82 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Your tests are still failing with this version. Compare changes Release Notes for 3.0.84
CommitsThe new version differs by 7 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 424 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for 3.2.1
CommitsThe new version differs by 724 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 752 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 757 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 770 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 824 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 875 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 896 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 931 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for 3.2.9
CommitsThe new version differs by 935 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 967 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 978 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 994 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 1004 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 1021 commits.
There are 250 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for 3.2.15CommitsThe new version differs by 1051 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for 3.2.16
CommitsThe new version differs by 4 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 21 commits.
There are 21 commits in total. See the full diff |
1 similar comment
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 21 commits.
There are 21 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for 3.2.18CommitsThe new version differs by 41 commits.
There are 41 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 70 commits.
There are 70 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 72 commits.
There are 72 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for 3.2.21
CommitsThe new version differs by 137 commits.
There are 137 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for 3.2.22
CommitsThe new version differs by 148 commits.
There are 148 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 167 commits.
There are 167 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for 3.2.24
CommitsThe new version differs by 169 commits.
There are 169 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for 3.2.25
CommitsThe new version differs by 172 commits.
There are 172 commits in total. See the full diff |
The devDependency esm was updated from
3.0.82
to3.0.83
.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
esm is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
Commits
The new version differs by 73 commits.
82f4a8d
Bump to v3.0.83.
c7d1225
Add ESM_DISABLE_CACHE to readme.
9339890
Add ext priority test for options.cjs.paths.
85cd3c1
Remove unused assert import from ext tests.
b73ca44
Destructure error code in tests.
ab1aba5
Make ext tests use the actual ext.
04e567c
Cleanup Entry#addGetterFrom(), Runtime.addExportFromSetter(), and Runtime.addNamespaceSetter().
0d7117c
Remove ERR_MODULE_RESOLUTION_LEGACY guard from makeRequireFunction().
e980f7d
Remove isError() and options.cjs.paths guard from tryParse().
608a625
Minor format Entry format nits.
ea100b1
Remove isError() guards for errors coming from esm/validate.
38accbe
Use Map for the stat cache.
4419e2d
Minor dummyProxy class cleanup.
96c8257
Use maps for memoize caches.
d0a33f6
Ensure .cache folder is cleared before the first test run.
There are 73 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: