Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bugger parity #2

Open
17 of 21 tasks
jkrems opened this issue Nov 13, 2015 · 0 comments
Open
17 of 21 tasks

Bugger parity #2

jkrems opened this issue Nov 13, 2015 · 0 comments

Comments

@jkrems
Copy link
Contributor

jkrems commented Nov 13, 2015

  • Step-by-step debugging
  • Variable introspection
  • Support for console API
  • Evalute expressions in the console
  • Monitor outgoing http(s) requests your script does (Network tab)
  • Heap snapshots and CPU profiles (Profiles tab)
  • Live edit the running JavaScript code
  • Break on exception
  • Break on uncaught exception
  • --brk to stop at the first line
  • Continue to location
  • Disable/enable all breakpoints
  • Track heap allocations
  • Shows up in chrome://inspect
  • Source maps aren't recognized correctly

Known issues

  • Reconnecting in paused state does not send the backtrace correctly
  • The timeline tab doesn't do anything useful right now (e.g. console.{time, timeEnd, timeStamp}, network request and heap usage reporting aren't working). Profiling data is collected but not really displayed.
  • For babel-core/register and coffee-script/register, editing the files doesn't work
  • Break event handling doesn't report on the breakpoints involved
  • Doesn't have a fancy website
  • Impossible to pass V8 flags (and other options) into CLI tool
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant