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

lc2-report

v1.1.4

Published

> all report info stores in report.zip. The directory structure of report.zip is as follows

Downloads

5

Readme

lc2-report

persistent storage

all report info stores in report.zip. The directory structure of report.zip is as follows

+- report.zip
|- report.log
|- meta.json
|+ screenshot // All capture
 |- capture1.png
 |- capture2.png
 `- ...
|+ sources // All *.lc2 with directory
 | example.lc2
 `- <pathname> // relative to workspace
// The report.log file is as follows: each log object is a line.
// if there are too many logs, the file will be split into
// another. All the file names can be got from report.json.
{"type": "start","data": {...},"time": 1477492497167}
{"type": "jumpto","data": {"url": "https://www.baidu.com/","line": 7},"time": 1477492498273}
...
{"type": "end","data": {"time": 1477492499401},"time": 1477492499401},

data structure

{
	meta: {
		title: xxx,
		start: xxx, // suite start time
		pass: xxx,  // number of case passed
		fail: xxx,  // number of case failed
		tmpDir: xxx // tmp directory to unzip the report.zip
	},
	caseList: [
		{
			root: xxx, // root path of the case
			path: xxx, // path of the code
			code: xxx, // code of case,
			failIndex: xxx, // which log failed
			duration: xxx, // runtime of this case
			logList: [
				{
					type: 'start',
					time: xxx
				},
				{
					type: 'lc2Code', // code resource
					time: xxx, // time of this log
					data: {
						name: xxx,
						path: xxx, // code resource path
					}
				},
				{
					type: 'runtimeJS',
					time: xxx,
					data: {
						line: xxx,
						message: xxx
					}
				},
				{
					type: 'runtimeDriver',
					time: xxx,
					data: {
						action: xxx,
						line: xxx,
						success: xxx,
						selector: xxx,
						duration: xxx,
						param: xxx
					}
				},
				{
					type: 'runtimeLC2',
					time: xxx,
					data: {
						action: xxx,
						line: xxx,
						data: {
						}
					}
				},
				{
					type: 'capture',
					time: xxx,
					data: {
						path: xxx  // path of the capture
					}
				},
				{
					type: 'end',
					time: xxx
				}
			]
		}
	]
}