bpytlik

In the current code, if the user uses an option that doesn't exist, here's how the error gets thrown: ``` throw new Error(format('unknown option: "--%s"', name)); ``` The main difficulty...

setRecordingProfile is going away in DevTools front ends

3

In issue [106252002](https://codereview.chromium.org/106353002/) setRecordingProfile was removed from DevTools front ends as an interface. According to an email exchange I had, it's been replaced by '... Profile.consoleProfileStarted/consoleProfileFinished events to signal front-end...

Feature Request :: programmatic support for named profiles

2

I can programmatically start and stop profiling using constructions like this: ``` agent.loadedAgents["Profiler"].start({}, () ->) ``` The v8-profiler [`startProfiling` function](https://github.com/c4milo/node-webkit-agent/blob/master/lib/v8-profiler.js#L212) supports providing a name for a profile, but the [Profiler...

startProfiling and stopProfiling should agree on the default name

2

In [v8-profiler.js](https://github.com/c4milo/node-webkit-agent/blob/master/lib/v8-profiler.js) it seems like [startProfiling](https://github.com/c4milo/node-webkit-agent/blob/master/lib/v8-profiler.js#L212) sets the default name to be ``` name = 'org.nodejs.profiles.cpu.user-initiated.' + (cpuCache.length + 1); ``` Meanwhile, [stopProfiling](https://github.com/c4milo/node-webkit-agent/blob/master/lib/v8-profiler.js#L220) sets the default name to be ''....

improve output on invalid JSON in an example

1

When an example isn't valid JSON, the error you get looks like this: AssertionError: Invalid JSON: undefined Error: expected [Function] to not throw an error but 'SyntaxError: Unexpected string' was...