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

@djaty/djaty-cli

v1.0.3-beta

Published

Djaty CLI

Downloads

1

Readme

Djaty Cli

Installation

  • $ npm install -g @djaty/djaty-cli

Prerequisites

We support node version 6.x.x or higher.

SourceMap files

Upload sourcemap files to allow Djaty to de-obfuscate your JavaScript stack traces

This lets you view source code context obtained from stack traces in their original untransformed form, which is particularly useful for debugging minified code (e.g. UglifyJS), or transpiled code from a higher-level language (e.g. TypeScript, ...).

Uploading sourcemap

djaty-cli uploadSourcemap [options]

  • --api-key: An API key for project.
  • --api-secret: An API secret for project.
  • --release: when requesting to resolve a stack trace, we check the bug release against current uploaded releases and if a release is matched, the stack trace will be resolved. So, if a bug is not configured with a release, it'll not be able to have its stack trace resolved. And due to the probability of having multiple devices running different releases concurrently, we let the user upload up to 5 releases per project.
  • --minified-dir: Path to the directory that contains the minified and sourcemap files (I.e, dist). Only .js and .map files will be uploaded.
  • --project-root: The path of the project root. It helps us locate the original files from the stack frame, e.g., http://example.com.
  • --end-point: The server URL The default is djaty.com (on-premises installations).

Example

$ djaty-cli uploadSourcemap --api-key <project-api-key> \
--api-secret <project-api-secret> --release <release> --minified-dir <dir-path> \
--project-root https://your-domain.com

Development

  • $ npm install
  • $ npm start

Developer notes:

  • We should add all dependencies and devDependencies in package.json as dependencies to be able to build the cli after installation.