</>PackageGraphPackageGraph

chrome-trace-event

npmv1.0.4TypeScript

A library to create a trace of your node app per Google's Trace Event format.

Adopt with care

chrome-trace-event is usable, with caveats. Last published 833 days ago.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • DMaintenance: grade D, Poor — a real concern.

    Last published 833 days ago.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 9.6 KB installed.

  • ASupply chain: grade A, Excellent.

    No install scripts, 2 maintainers, and a contained dependency surface.

  • ALicense: grade A, Excellent.

    MIT — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding chrome-trace-event to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

9.6 KB
Install size

Unpacked size of this package plus its entire runtime tree.

—
Tree depth

Longest resolved dependency chain below this package.

Compatibility

Node.js
node >=6.0
Module format
CommonJS only
TypeScript
Types included
Install scripts
None

Quick start

A usage example from the chrome-trace-event README.

javascriptFull README ↗
const Trace = require("chrome-trace-event").Tracer;
const trace = new Trace({
    noStream: true
});
trace.pipe(fs.createWriteStream(outPath));
trace.flush();

chrome-trace-event vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
chrome-trace-eventthis page01MIT2 years ago
callsites157.5M1MIT3 days ago
rettime02MIT3 days ago
gcp-metadata01Apache-2.03 days ago
gaxios01Apache-2.03 days ago
event-target-shim02MIT3 days ago

Dependencies

Declared by chrome-trace-event v1.0.4. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (4)

@types/node *prettier ^1.12.1tape 4.8.0typescript ^4.2.4

Used by

Popular packages that depend on chrome-trace-event.

webpacknpm

Packs ECMAScript/CommonJs/AMD modules for the browser. Allows you to split your codebase into multiple bundles, which can be loaded on demand. Supports loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff.

↓ 56.4M/wk◈ 29 dependents⚖ MITTS

Relationship graph

Dependencies (left) and dependents (right) of chrome-trace-event.

webpackchrome-trace-event
chrome-trace-event dependencies dependents

Frequently installed together

acornnpm

ECMAScript parser

↓ 254.2M/wk◈ 19 dependents⚖ MITTS
@types/estreenpm

TypeScript definitions for estree

↓ 220.5M/wk◈ 12 dependents⚖ MITTS
browserslistnpm

Share target browsers between different front-end tools, like Autoprefixer, Stylelint and babel-env-preset

↓ 194M/wk◈ 5 dependents⚖ MITTS
lodashnpm

Lodash modular utilities.

↓ 173.7M/wk◈ 20 dependents⚖ MIT
reactnpm

React is a JavaScript library for building user interfaces.

↓ 171.6M/wk◈ 82 dependents⚖ MIT
react-domnpm

React package for working with the DOM.

↓ 161.2M/wk◈ 47 dependents⚖ MIT
eslintnpm

An AST-based pattern checker for JavaScript.

↓ 159.4M/wk◈ 277 dependents⚖ MITTS
enhanced-resolvenpm

Offers a async require.resolve function. It's highly configurable.

↓ 137.3M/wk◈ 1 dependents⚖ MITTS
prettiernpm

Prettier is an opinionated code formatter

↓ 132.4M/wk◈ 159 dependents⚖ MITTS
eventsnpm

Node's event emitter for all engines.

↓ 92.3M/wk◈ 2 dependents⚖ MIT
jestnpm

Delightful JavaScript Testing.

↓ 48M/wk◈ 70 dependents⚖ MITTS
eslint-scopenpm

ECMAScript scope analyzer for ESLint

↓ 0/wk◈ 2 dependents⚖ BSD-2-ClauseTS

Release history

No releases in the last two years, typically about 61 days apart.

Recent versions of chrome-trace-event
VersionPublishedSizeLicense
1.0.4latest2 years ago9.6 KBMIT
1.0.35 years ago14 KBMIT
1.0.27 years ago17 KBMIT
1.0.17 years ago24 KBMIT
1.0.08 years ago25 KBMIT
0.1.38 years ago15 KBMIT
0.1.28 years ago15 KBMIT
0.1.18 years ago—MIT
0.1.08 years ago—MIT

Overview

chrome-trace-event is an npm package that a library to create a trace of your node app per Google's Trace Event format. It has 1 known dependents in the graph. The latest version is 1.0.4, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need a library to create a trace of your node app per Google's Trace Event format and value a focused solution.

When not to use it

Consider an alternative if you need to or if a more actively-maintained option better fits your npm stack.

Pros

  • Ships TypeScript type definitions.
  • Clear open-source license (MIT).

Cons

  • No significant drawbacks detected from available metadata.

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

samcconesusielu

Keywords

eventgoogletracetrace-eventtrace-viewer

Frequently asked questions

Should I use chrome-trace-event?

chrome-trace-event is usable, with caveats. Last published 833 days ago.

How do I install chrome-trace-event?

Run `npm install chrome-trace-event` to add chrome-trace-event to your npm project.

What license is chrome-trace-event released under?

chrome-trace-event is distributed under the MIT license.

How popular is chrome-trace-event?

npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on chrome-trace-event.

Is chrome-trace-event still maintained?

The most recent release of chrome-trace-event (v1.0.4) was published 2 years ago.

Does chrome-trace-event run install scripts?

No. chrome-trace-event does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.