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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@pacy-dev/plugin-devtools

v0.0.2

Published

Framework configuration plugin for Pacy DevTools

Readme

@pacy-dev/plugin-devtools

Pacy DevTools works out of the box with vite-react, vite-vue-3, and vite-svelte boilerplates, Remix, and Next.js v14 (without Turbo). For supporting other bundlers and frameworks, this plugin can be used.

First of all, this plugin uses code-inspector internally. It supports bundlers such as Webpack, Vite, Rspack / Rsbuild, Esbuild, Next.js and Nuxt, and it can be used to support Vue 2, Next.js v15 (without Turbo), and frameworks such as Preact, Solid, Astro, and Qwik.

It can also be used to troubleshoot problems with some vite-react, vite-vue-3, and vite-svelte configurations that might have broken sourcemaps. This plugin adds DOM sourcemaps to elements, and Pacy DevTools will use them over any other sourcemap whenever they're available.

Usage

This section is mostly taken from code-inspector's documentation. You can check their configuration instructions here.

// webpack.config.js
import pacyDevtools from '@pacy-dev/plugin-devtools';

module.exports = () => ({
  plugins: [
    pacyDevtools({
      bundler: 'webpack',
    }),
  ],
});
// vite.config.js
import { defineConfig } from 'vite';
import { pacyDevtools } from '@pacy-dev/plugin-devtools';

export default defineConfig({
  plugins: [
    pacyDevtools({
      bundler: 'vite',
    }),
  ],
});
// rspack.config.js
import pacyDevtools from '@pacy-dev/plugin-devtools';

module.exports = {
  // other config...
  plugins: [
    pacyDevtools({
      bundler: 'rspack',
    }),
    // other plugins...
  ],
};
// rsbuild.config.js
import pacyDevtools from '@pacy-dev/plugin-devtools';

module.exports = {
  // other config...
  tools: {
    rspack: {
      plugins: [
        pacyDevtools({
          bundler: 'rspack',
        }),
      ],
    },
  },
};
// esbuild.config.js
const esbuild = require('esbuild');
import pacyDevtools from '@pacy-dev/plugin-devtools';

esbuild.build({
  // other configs...
  plugins: [pacyDevtools({ bundler: 'esbuild', dev: () => true })],
});
// vue.config.js
import pacyDevtools from '@pacy-dev/plugin-devtools';

module.exports = {
  // ...other code
  chainWebpack: (config) => {
    config.plugin('@pacy-dev/plugin-devtools').use(
      pacyDevtools({
        bundler: 'webpack',
      })
    );
  },
};

For nuxt3.x :

// nuxt.config.js
import { pacyDevtools } from '@pacy-dev/plugin-devtools';

// https://nuxt.com/docs/api/configuration/nuxt-config
export default defineNuxtConfig({
  vite: {
    plugins: [pacyDevtools({ bundler: 'vite' })],
  },
});

For nuxt2.x :

// nuxt.config.js
import { pacyDevtools } from '@pacy-dev/plugin-devtools';

export default {
  build: {
    extend(config) {
      config.plugins.push(pacyDevtools({ bundler: 'webpack' }));
      return config;
    },
  },
};

Next.js ≤ 14.x

// next.config.js
const pacyDevtools = require('@pacy-dev/plugin-devtools');

const nextConfig = {
  webpack: (config, { dev, isServer }) => {
    config.plugins.push(pacyDevtools({ bundler: 'webpack' }));
    return config;
  },
};

module.exports = nextConfig;

Next.js 15.0.x ~ 15.2.x

// next.config.js
import type { NextConfig } from 'next';
const pacyDevtools = require('@pacy-dev/plugin-devtools');

const nextConfig: NextConfig = {
  experimental: {
    turbo: {
      rules: pacyDevtools({
        bundler: 'turbopack',
      }),
    },
  },
};

export default nextConfig;

Next.js ≥ 15.3.x

// next.config.js
import type { NextConfig } from 'next';
const pacyDevtools = require('@pacy-dev/plugin-devtools');

const nextConfig: NextConfig = {
  turbopack: {
    rules: pacyDevtools({
      bundler: 'turbopack',
    }),
  },
};

export default nextConfig;

In some Next.js versions, Turbopack can be on or off via the --turbopack flag in package.json (e.g. "dev": "next dev --turbopack"). Before setting the bundler option to turbopack or webpack, be sure to check the dev command in package.json.

// astro.config.mjs
import { defineConfig } from 'astro/config';
import { pacyDevtools } from '@pacy-dev/plugin-devtools';

export default defineConfig({
  vite: {
    plugins: [pacyDevtools({ bundler: 'vite' })],
  },
});

Acknowledgement

This plugin relies on code-inspector internally, with following settings:

hideDomPathAttr: true,
hotKeys: false,
hideConsole: true,
pathType: 'absolute'