Closed greenkeeper[bot] closed 6 years ago
Merging #6 into master will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #6 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 1 1
Lines 21 21
=====================================
Hits 21 21
Continue to review full report at Codecov.
Legend - Click here to learn more
Ī = absolute <relative> (impact)
,Ćø = not affected
,? = missing data
Powered by Codecov. Last update e84b015...b1b295d. Read the comment docs.
Update to this version instead š
The new version differs by 26 commits.
f407b6a
Bump to v0.23.1.
723cd8e
Revert webpack 4 upgrade to fix nodechakra test fails.
ced04e5
Upgrade to webpack v4.
1127efb
Cleanup scenario tests.
c51dd10
Ensure _findPath cache distinguishes between cjs and esm. [closes #296]
7cc880a
Separate resolveFilename cache by cjs/esm.
14a0a8f
Wrap mkdirSync use in index.js in a try-catch to avoid EACCES errors in some environments. [closes #297]
8ef6aa5
Make proxy handler look empty instead of invisible.
aee96db
Remove unneeded config from ava-nyc scenario test.
a9649d3
Ensure proxies are unwrapped for modules with CJS interop unlocked. [closes #294]
a6cd8f4
Remove unneeded nested directory in dual scenario test.
5b6d86e
Add std/esmās autoloaded builtin modules to the repl.
11cf4c4
Sort Module.builtinModules.
0720e91
Add util.inspect mask for REPL use.
c527b92
Remove Node 4 guards from export-tests.
There are 26 commits in total.
See the full diff
āļø Greenkeeperās updated Terms of Service will come into effect on April 6th, 2018.
Version 0.23.0 of @std/esm was just published.
The version 0.23.0 is not covered by your current version range.
If you donāt accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of @std/esm.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you donāt have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 64 commits.
76cfe85
Bump to v0.23.0.
24b848f
Ensure native methods are unwrapped for Function#toString calls.
090ccf1
Split out getProxyDetails() from isProxy().
40671a0
Track proxy details in OwnProxy.
3aaf52d
Skip jest test in chakra until the jest regression is resolved.
bdbef0c
Enable shim for global context when just initialized to catch the repl case.
8cdaebd
Add prefix constants.
34d8385
Move constants to their own folder.
7a959ae
Avoid CJS live binding test fail in chakra.
6b066b9
Add chars constants.
dfa7781
Make own proxies more generally detectable.
66c1c9d
Split builtin modules into safe and utils.
f08e4db
Rename ascii constants to char_codes.
bd8cc6f
Update deps.
c7f9326
Add OwnProxy class.
There are 64 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: