Closed greenkeeper[bot] closed 5 years ago
After pinning to 3.2.11 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
devDependency
esm was updated from 3.2.12
to 3.2.13
.Your tests are still failing with this version. Compare changes
The new version differs by 10 commits.
ccad0c6
Bump to v3.2.13.
23c5d19
Update deps.
3ea8860
Fix tests in Node < 11.
666c08d
Check that console methods are bound before adding them to the method map.
f405d10
Add isBound().
75d64c1
Extract isNativeLike().
ce7336a
Set prototype of sideloaded module before exiting early in module hook.
9939f0c
Avoid module._compile wrapping when loading cached code.
da6e263
Clarify checks to use Module._extensions in esm/loader.
8440d9f
Var name nit.
See the full diff
devDependency
esm was updated from 3.2.13
to 3.2.14
.Your tests are passing again with this update. Explicitly upgrade to this version 🚀
The new version differs by 17 commits.
e8e17d1
Bump to v3.2.14.
3d7fab3
Readme tweaks.
37aee5d
Return values of tryPassthru().
5ab620c
Use sideloaded compile wrapper if it exists. [closes #739]
3cf1b9c
Update tagline in readme.
ce55266
Cleanup V8 bug comments.
23a163a
Avoid V8 tail call optimization bug with --harmony flag in Node 6.
f1a4361
Avoid exposing private realm to inspect().
e861807
Use more toExternalFunction() in OwnProxy().
e5dc24f
Import order nit.
fd262ef
Use setProperty() in shims.
92de1ab
Add comment for natives binding use.
bf4fb2b
Use safeProcess in src/module/esm/extensions and src/caching-compiler.
2d28cb4
Use safeProcess in src/binding.
8233b80
Add safeProcess methods.
There are 17 commits in total.
See the full diff
bogus Java nonsense
The devDependency esm was updated from
3.2.11
to3.2.12
.🚨 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
- ❌ **continuous-integration/travis-ci/push:** The Travis CI build could not complete due to an error ([Details](https://travis-ci.org/complate/complate-stream/builds/503372306?utm_source=github_status&utm_medium=notification)).Commits
The new version differs by 16 commits.
33cafee
Bump to v3.2.12.
d6c6414
Update deps.
a0b2375
Don't project over custom console methods provided by the runtime. [closes #737]
d53f38d
Var order nit.
fa8644d
Remove @babel/register dirty cache guard.
8b8bcd1
Use fallback content for mod._compile() if provided.
3ea7eef
Use setProperty() and toExternalFunction() when setting mod._compile().
d19a517
Use more toExternalError().
a183ab4
Mask errors in Module._preloadModules().
42115e9
Cleanup error masking branches.
fbb22d6
Move entry._passthruCompile reset to the same module it's set in.
4453156
Lint nit.
94a8e7c
Track entry._ranthruCompile.
7a37941
Whitespace nit.
c42eaf1
Avoid running code through a possible transform pipeline when compile cached.
There are 16 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: