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

nextlevelpackage

v1.0.7

Published

this package will connect you to the nextlevel dashboard

Downloads

14

Readme

Getting Started

  1. To get started, visit nextlevel-dash.com and create an account. After account creation, you will be navigated to an onboardingp page which will direct you to complete the below steps.

  2. Install configure next.js bundle analyzer in your Next.js application

    NPM install Next.js Bundle Analyzer:

    npm install @next/bundle-analyzer

    Configure next.config.mjs file:

    import pkg from '@next/bundle-analyzer';
    const withBundleAnalyzer = pkg({
        enabled: process.env.ANALYZE === 'true',
    });
    
    const nextConfig = {};
    
    export default withBundleAnalyzer(nextConfig);
  3. Install and configure our npm package, NextLevelPackage, through the terminal. It can also be found here.

    NPM Install NextLevelPackage:

    npm install nextlevelpackage

    Import NextLevelPackage in layout.js:

    import NextWebVitals from 'nextlevelpackage';

    Add NextWebVitals component in RootLayout body:

    export default function RootLayout({ children }) {
        return (
            <html lang="en">
            <body>
                <NextWebVitals />
                {children}
            </body>
            </html>
        );
    }
  4. Configure yoour Environmental Variables

    Add the following line to your .env.local file:

    NEXT_PUBLIC_API_KEY=<your-api-key>

    When you create an account, the setup page will provide you with your API key.

  5. Add Build Script to package.json

    Add the following script to your package.json:

    "scripts": {
        "nextlevelbuild": "node ./node_modules/nextlevelpackage/cli.js"
    }

    Run this build script instead of 'npm next build' to track metrics in the dashboard:

    npm run nextlevelbuild
  6. Navitage to your NextLevel dashboard to view tracked metrics!

Tracked Metrics

Metrics displayed on the page include:

  • Time to First Byte:
    • measures the time taken from a user's request to the first byte of data received from the server, indicating server responsiveness.
  • Largest Contentful Paint:
    • gauges the time it takes for the largest visible content element on a webpage to load, impacting user perception of loading speed.
  • First Contentful Paint:
    • tracks the time from page load to when the first piece of content is rendered on the screen, marking the start of the visual loading process.
  • First Input Delay:
    • measures the delay between the user's first interaction with the page and the browser's response, reflecting input responsiveness.
  • Interaction to Next Paint:
    • evaluates the time from user interaction to the next visual update, assessing how quickly a page responds to user inputs.
  • Cumulative Layout Shift:
    • quantifies the total of all individual layout shifts that occur during the entire lifespan of the page, indicating visual stability.
  • Build Time:
    • refers to the duration taken to compile and bundle code and assets into a deployable format during the development process.
  • Bundle Size:
    • denotes the total size of all the compiled assets sent to the client, affecting load times and overall performance.