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

@dodona/trace-component

v1.1.6

Published

- [Trace component](#trace-component) - [Usage](#usage) - [CSS variables](#css-variables) - [Contributing](#contributing) - [Setup](#setup) - [Build](#build) - [Dev Server](#dev-server)

Downloads

297

Readme

Table of contents

Trace component

Trace component is a modern webcomponent that visualizes the trace of a program. It is reimplementation of pythontutor. All credits for the original idea go to Philip Guo.

img.png

Usage

To use the webcomponent, import the js and simply use the component in your html:

<tc-trace .trace=${trace} .translations="translations"></tc-trace>

This trace is preferably generated by our json tracer. But you can write your own trace generator as long as it follows the format specified in our types. This component should also be compatible with the pythontutor trace format for now, but this might change in the future.

translations is an optional object that can be used to translate the information card shown at the first frame. It should be of type HelpCardTranslations as defined in HelpCard.ts.

You can listen to frame-change events to get the current frame of the trace for example to indicate the current line of code.

You can also add your trace frame by frame using the addFrame method. This method takes a Frame as defined in types.

const traceComponent = document.querySelector('tc-trace');
traceComponent.addFrame({...});

CSS variables

To adjust the look of the trace, you can adjust the css variables defined in the styles file.

Contributing

Setup

Install dependencies:

yarn install

Build

To build the JavaScript version of your component:

yarn build

To watch files and rebuild when the files are modified, run the following command in a separate shell:

yarn build:watch

Dev Server

This project uses modern-web.dev's @web/dev-server for previewing the project without additional build steps. Web Dev Server handles resolving Node-style "bare" import specifiers, which aren't supported in browsers. It also automatically transpiles JavaScript and adds polyfills to support older browsers. See modern-web.dev's Web Dev Server documentation for more information.

To run the dev server and open the project in a new browser tab:

yarn serve

There is a development HTML file located at /dev/index.html that you can view at http://localhost:8000/dev/index.html. Note that this command will serve your code using Lit's development mode (with more verbose errors). To serve your code against Lit's production mode, use yarn serve:prod.