DevTools front-end expects to receive Page.getResourceTree response
before any "scriptParsed" events. When "scriptParsed" arrives first,
the source-map handler throws an exception.
Add FrontendClient methods pauseEvents() and resumeEvents().
Change PageAgent to EventEmitter, add a "resource-tree" event that
is emitted at the time when the Page.getResourceTree response is sent.
FrontendCommandHandler uses these two features to pause events on start
and resume them on "resource-tree".
Changed the socket implementation to use WS-server, and added
utility function to generate the web socket url with the correct
protocol and relative path.
- Registered additional no-op commands
- Added `column` property to console log messages
- Disabled warning about changes not persisted to filesystem
- Added `hitBreakpoints` to `Debugger.paused` message
- Simplified Debugger._handleChangeLiveOrRestartFrameResponse by removing
stepIntoAndSendResponse(), as this is handled by front-end now
- Removed patch for `loadXHR()` and implememented source-maps loading using
the new command `Network.loadResourceForFrontend`.
Modified FrontendCommandHandler so that it returns an error response for
methods not implemented.
Modified FrontendClient to send a log message to front-end when a request
failed.
Moved debugger-related code from session to DebuggerClient.
Moved sendDebugRequest from debugger to DebuggerClient.
Fixed a bug where a front-end page served from an old node-inspector
process crashed the new node-inspector process after restart.
Moved methods like sendResponse, sendEvent, etc. to FrontendClient.
Modified Agents and FrontendCommandHandler to use this new object
instead of session.
Removed ping message since it is no longer needed (socket.io can keep
the connection alive or handle reconnect).