npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

ti-debug

v0.2.1

Published

Server-side components for WebKit Remote Debugging

Downloads

9

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

dpb587dpb587

Keywords

Readme

Server-side debugging engines using the WebKit remote debugger.

Prerequisites

At a minimum this requires node and npm to get started. I am currently using:

$ node -v
v0.10.1
$ npm -v
1.2.15

For best results, use a recent WebKit-based browser like Google Chrome or Apple Safari to connect to the ti-debug server.

Installation

git clone https://github.com/dpb587/ti-debug
cd ti-debug/
npm install

Usage

By default bin/ti-debug will start a web server on localhost:9222 for you to connect and get started debugging. When a new debug session is available the page will redirect to the debugging tools for the session. To see a full list of configuration options run bin/ti-debug --help.

DBGp

The DBGp service is enabled by default. Simple run bin/ti-debug, point your browser to localhost:9222, and configure your DBGp engine to connect to the DBGp client at localhost:9000. If you need to support multiple developers, enable the DBGp proxy server by adding the --dbgp-proxy option to the command - both browser-based and IDEs are supported.

PHP

You'll probably want to ensure the xdebug extension is installed and configured.

See Also:

Python

You'll probably want to ensure the komodo-remote-debugging module is installed. Be sure to invoke scripts with the included pydbgp.

See Also:

Functionality

✓ – full support
‡ – partial support
✕ – no support

Architecture

The main purpose of ti-debug is to allow debugging protocols to be accessible through a browser interface. Currently the WebKit Inspector powers the interface and communications occur:

frontend debugger <-- frontend protocol --> ti-debug <-- debugger protocol --> debugger engine

In the case of DBGp, a client is started to wait for connections from the DBGp server. When a connection is received, it checks to see if there's a browser waiting to debug and creates a debug session for the browser to connect to. From there, Inspector-friendly agents handle translating DBGp commands into WebKit commands. For example:

References

Credits

License

MIT License