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

@conga/framework-profiler

v2.1.0

Published

Conga.js profiler bundle

Downloads

14

Readme

@conga/framework-profiler

Add runtime profiling to your CongaJS application.

See the documentation for more information.

Configuration

profiler:
    
    # optional, if omitted, true is used
    # possible values are true, false, request
    # request means, only enabled for matched requests
    enabled: request
    
    # required
    bass:
        manager: default.nedb
    
    # optional, if omitted, true is used with defaults
    monitoring:
        # whether or not to enable stat monitoring
        # even if this is true, profiler.enabled must be set to either true or request or monitoring will not run 
        enabled: true
        
        # tells the ProfilerStatService how often to check for stats when there are no active requests
        delay_idle: 1000
        
        # tells the ProfilerStatService how often to check for stats when there is 1 or more active requests 
        delay_request: 50
        
        # tells the ProfilerStatService how to persist the stats - possible values are "all" and "request"  
        # request meaning only persist the stats that occur during a request
        # all meaning persist every stat
        persist: request
    
    # optional
    security:
        authenticator: '@security.firewall.authenticator.http_basic'
        provider:
            memory:
                users:
                    profiler:
                        password: let-me-in
                        roles: ROLE_PROFILER
    # optional
    # even if not enabled, matchers may trigger a profiler on a request
    matchers:
        local:
            ip: 127.0.0.1
        
        foo:
            route: ^/api/blah/some/component
        
        bar: '@service.id'
    
    # optional
    # if you are working on the dashboard and want to profile the requests
    profile_dashboard: true