Michał Gołębiowski-Owczarek

You're right, there's no support for `npm-shrinkwrap.json` here. This module's main purpose is to be as fast as possible when checking for dependency correctness so it checks for the proper...

I think I'd be fine with such a feature. A few notes, though, before anyone tries to have a shot at this: 1. This should be hidden behind an option...

Thanks for the report. This behaves exactly as in the [`semver`](https://www.npmjs.com/package/semver) package: ```js const semver = require('semver'); semver.satisfies("1.2.3", "*"); // true semver.satisfies("1.2.3-beta.1", "*"); // false ``` The rationale is that...

Sounds reasonable. Would you like to prepare a PR?

That's true, this hasn't been implemented yet. I mostly did this module for npm where this feature doesn't exist and added bower support later. PRs welcome!

PR welcome. :) Be sure to add a test.

It's mapped by Git internally. Git consults the `.mailmap` when you do `git blame`, when you report commit stats via `git shortlog -nse` etc.

I think `core-js` should continue to provide an ES6 environment, at least by default; `fetch` is a DOM standard so that would be vastly different. If you start polyfilling the...

I agree with @ljharb that time is not an accurate measurement of obsoleteness. That said, it would be tedious to continually debate whether some Chrome version stops being widely used...

You can change the prototype after the definition: ``` js const o1 = { f(a, b) { console.log(a, b); } }; const o2 = { f(a) { super.f(1, a); },...