Ran Yitzhaki 8fce3195d6 fix(Launcher): exit the process after killing chrome on SIGINT (#2428) ... This is a fix for this issue https://github.com/facebook/jest/issues/5748 In the issue, `puppeteer.launch` method is called from jest `globalSetup` script which [is running on the same process as jest](6a77ee37ec/packages/jest-cli/src/run_jest.js (L242)). Puppeteer catches `SIGINT` in order to kill chrome, but it also replaces the default behaviour of `SIGINT`, [which is to exit with status code 130](https://nodejs.org/dist/latest-v9.x/docs/api/all.html#process_signal_events). In jest's case, the process does not exit, which keeps the process hanging in a weird way. This PR makes sure that the process exits after killing chrome.		2018-04-25 15:29:14 -07:00
..
.eslintrc.js
Browser.js	Add Page.browser() method (#2387)	2018-04-17 10:37:17 -07:00
BrowserFetcher.js	fix(BrowserFetcher): ensure executable has proper permissions (#2342)	2018-04-10 14:11:59 -07:00
Connection.js	fix(Connection): do not assert that methods always have callbacks. (#2330)	2018-04-07 17:59:22 -07:00
Coverage.js
Dialog.js
ElementHandle.js
EmulationManager.js
ExecutionContext.js	fix(Page): fix Page.evaluate with Symbols in arrays (#2340)	2018-04-09 22:02:35 -07:00
externs.d.ts
FrameManager.js	fix(Page): Page.waitForNavigation should correctly handle mixed content (#2339)	2018-04-10 15:59:41 -07:00
helper.js
Input.js
Launcher.js	fix(Launcher): exit the process after killing chrome on SIGINT (#2428)	2018-04-25 15:29:14 -07:00
Multimap.js
NavigatorWatcher.js	fix(Page): support anchor navigation (#2338)	2018-04-09 23:38:20 -07:00
NetworkManager.js	fix(Network): explicitly throw on content request for redirect response (#2352)	2018-04-10 20:22:18 -07:00
Page.js	chore(deps): bump dependencies (#2397)	2018-04-17 14:51:03 -07:00
Pipe.js
Puppeteer.js
Target.js	Add Page.browser() method (#2387)	2018-04-17 10:37:17 -07:00
TaskQueue.js
Tracing.js	Chore: replace depracated 'new Buffer' with 'Buffer.from' (#2396)	2018-04-17 13:49:01 -07:00
USKeyboardLayout.js