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

@beincom/node-profile

v3.0.2

Published

``` npm install @beincom/node-profile # yarn add @beincom/node-profile ```

Downloads

67

Readme

Getting started

npm install @beincom/node-profile
# yarn add @beincom/node-profile

Usage

  # app.module.ts
  @Module({
    imports: [
      ProfileModule.forRootAsync({
        useFactory: (configService: ConfigService) => {
          const labels: Record<string, string | number> = {
            pod: process.env.pod,
            version: process.env.version,
          };

          const tags: Record<string, string> = {};

          const profileConfig: ProfileConfig = {
            serverAddress: pyroscope.serverAddress,
            applicationName: process.env.APP_NAME,
            tags: tags,
            heap: {
              samplingIntervalBytes: Number(process.env.HEAP_INTERVAL_BYTES), // 512 * 1024
              stackDepth: Number(process.env.HEAD_STACK_DEPTH), // Maximum is 64
            },
            wall: {
              samplingDurationMs: Number(process.env.WALL_DURATION), // 10 * 1000
              samplingIntervalMicros: Number(process.env.WALL_INTERVAL), // 10 * 1000 * 1000
            },
          };

          const profileService = new ProfileService(profileConfig);
          profileService.setWallLabels(labels);
          profileService.start();
          return profileService;
        },
        inject: [ConfigService],
      }),
    ],
    providers: [],
    exports: [],
  })
  export class AppModule {}

Test

# pyroscope-config.yaml
log-level: debug
storage:
  type: filesystem
  path: /var/lib/pyroscope
scrape-configs:
  - job-name: testing            # any name
    enabled-profiles: [cpu, mem] # cpu and mem for cpu and heap
    static-configs:
      - application: rideshare
        spy-name: nodespy        # make pyroscope know it's node profiles
        targets:
          - localhost:3001       # address of your scrape target
        labels:
          env: dev               # labels
# docker-compose.yaml
version: '3'

services:
  pyroscope:
    image: grafana/pyroscope:latest
    ports:
      - "4040:4040"
    environment:
      - PYROSCOPE_SERVER_TYPE=pyroscope
      - PYROSCOPE_STORAGE_TYPE=filesystem
      - PYROSCOPE_LOG_LEVEL=debug
      - PYROSCOPE_LISTEN_ADDR=0.0.0.0:4040
      - PYROSCOPE_STORAGE_PATH=/var/lib/pyroscope
      - PYROSCOPE_MODE=pull
    volumes:
      - pyroscope-data:/var/lib/pyroscope
      - ./pyroscope-config.yaml:/etc/pyroscope/pyroscope-config.yaml

volumes:
  pyroscope-data:
    driver: local
    driver_opts:
      type: 'none'
      o: 'bind'
      device: './pyroscope-data'
# Run this command:
docker-compose up -d --force-recreate
docker ps

Container

docker logs -f 6ba

Logs