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

@thundra/esbuild-plugin

v1.0.3

Published

The Esbuild plugin to help Thundra's Node.js agent.

Downloads

3

Readme

thundra-es-plugin

Installation

npm install --save-dev @thundra/esbuild-plugin

Usage

esbuild.js

/* eslint-disable @typescript-eslint/no-var-requires */
const { ThundraEsbuildPlugin } = require('@thundra/esbuild-plugin');

module.exports = {
  ...
  plugins: [
    ThundraEsbuildPlugin({
      traceableConfigs: [
        'src.*.*[traceLineByLine=true]', // activate line by line tracing for all files under src folder
      ]
    })
  ]
};

And then, in your Function definition in your stack, add the file above to your bundle configuration.

// ...
bundle: {
  esbuildConfig: {
    plugins: "esbuild.js",
  },
},
// ...

To use the plugin, 'ThundraEsbuildPlugin' must be used. Method will create a plugin for esbuild. This method takes argument like below.

| Name | Requirement | Description | --- | --- | --- | traceableConfigs | Required | Array of instrumentation defination string

Instrumentation definition strings must be in the <file-def>.<function-def>[parameter1=value1,parameter2=value2,...] format where the parameter definitions are optional. Asterisk character (*) in the <file-def> and <function-def> is supported.

Optional parameters that are specified between the brackets can be used to trace arguments and return values or to enable line by line tracing: traceArgs, traceReturnValue and traceLineByLine. You can use these parameters by setting them to true or false. By default all these parameters are set to false.

For example the value of a instrumentation definition string could be:

  • To trace for all functions in js or ts files under ./src: src.*.*
  • To trace all functions in js or ts files under ./src/service folder with arguments: src.service.*.*[traceArgs=true]
  • To trace functions which start with get in the js or ts files under ./src/service folder with arguments and return value: src.service.*.get*[traceArgs=true,traceReturnValue=true]
  • To enable TTD (Time Travel Debugging) for all functions in userService module (js or ts file) under ./src/service: src.service.userService.*[traceLineByLine=true]