[Snyk] Upgrade lie from 3.0.0 to 3.3.0 #3

snyk-bot · 2020-04-25T00:09:47Z

Snyk has created this PR to upgrade lie from 3.0.0 to 3.3.0.

✨What is Merge Advice?

We check thousands of dependency upgrade pull requests and CI tests every day to see which upgrades were successfully merged. After crunching this data, we give a recommendation on how safe we think the change is for you to merge without causing issues. Learn more, and share your feedback to help improve this feature. 🙏

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 8 versions ahead of your current version.
The recommended version was released 2 years ago, on 2018-03-06.

Release notes

Package name: lie

3.3.0 - 2018-03-06
fine I'll include some typescript junk
3.2.0 - 2018-01-29
Add finally method
3.1.1 - 2017-02-09
fix edge case related to spec: 2.3.3: "Otherwise, if x is an object or function"
3.1.0 - 2016-07-27
do browserify transforms as prepublish
3.0.4 - 2016-04-30
forgot to update the built files in v3.0.3
3.0.3 - 2016-04-30
should fix #32 plus it updates the es3ify dep that was relying on a dep that was breaking in newer npm versions
3.0.2 - 2016-01-21
3.0.2
3.0.1 - 2015-08-06
fixes #26 the WARN: Dropping unused variable UNHANDLED message generated by jshint
3.0.0 - 2015-07-30
Overall it should be very much in line with how es6 promises work in the browser/node and should be about 18% smaller now coming in at 1867 bytes minified and gzipped.
- BREAKING adds some es6 compatibility fixes to make inheriting possible, which now means Process.[all|race|resolve|reject] may not be called in an arbitrary context, i.e.
```
// WON'T WORK
var resolve = Promise.resolve;
var promise = resolve(true);
// STILL WORKS

var promise = Promise.resolve(true);
```
- BREAKING new is no longer optional for constructors, e.g.
```
// WON'T WORK
var foo = Promise();
// STILL WORKS

var foo = new Promise();
```
  this is exactly how es6 promises work
- resolve no longer caches falsy promises, this was of minimal perf benefit and could cause global issues issues if somebody was to screw around with one of those cached promises as they were global and mutable, this is theoretically breaking, but honestly you'd have to be doing something pretty dumb for this to be a breaking change in your code.
- no longer broken into many modules, this doesn't effect performance or how it works in any way, but makes it a lot smaller as the library is small enough that all the wrapping functions added up to a noticeable fraction of the total library size