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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@pinia/colada-devtools

v2.0.0

Published

Devtools for Pinia Colada

Readme

Pinia Colada Devtools

Migrating from v1 to v2

Version 2 moves the devtools out of your Vue component tree and into Vite. Keep @pinia/colada-devtools as a development dependency, then remove the v1 component from your app:

 <script setup lang="ts">
-import { PiniaColadaDevtools } from '@pinia/colada-devtools'
 </script>

 <template>
   <RouterView />
-  <PiniaColadaDevtools />
 </template>

If you used <PiniaColadaProdDevtools />, remove it in the same way and enable production support in the Vite plugin as described below.

Vite DevTools

Use this when your project uses the new Vite DevTools:

pnpm add -D @pinia/colada-devtools @vitejs/devtools @vitejs/devtools-kit
+import { DevTools } from '@vitejs/devtools'
+import { PiniaColadaDevtools } from '@pinia/colada-devtools/vite'

 export default defineConfig({
-  plugins: [vue()],
+  plugins: [vue(), DevTools(), PiniaColadaDevtools()],
 })

The Pinia Colada plugin must come after DevTools().

Use Vite DevTools and its kit version 0.7.5 or later with DevFrame 1.

For Nuxt, install @pinia/colada-devtools and enable Nuxt DevTools. The Pinia Colada Nuxt module registers the integration automatically:

 export default defineNuxtConfig({
   modules: ['@pinia/nuxt', '@pinia/colada-nuxt'],
+  devtools: { enabled: true },
 })

Standalone

If the project does not use Vite DevTools, use the standalone DevFrame UI:

pnpm add -D @pinia/colada-devtools @devframes/hub @devframes/hub-ui @devframes/vite
+import { PiniaColadaDevtoolsStandalone } from '@pinia/colada-devtools/standalone'

 export default defineConfig({
-  plugins: [vue()],
+  plugins: [vue(), PiniaColadaDevtoolsStandalone()],
 })

MCP support is included through @devframes/agentic. The standalone host enables MCP; a custom hub controls MCP through its own mcp option. The Vite and standalone adapters publish their live hub to devframe connect. Browser-backed tools are available while an app page is open and authorized.

Production builds

To keep the devtools in production, enable both options in your Vite configuration:

plugins: [vue(), DevTools({ build: { withApp: true } }), PiniaColadaDevtools({ production: true })]

Load <base>__devtools/embedded.js in the built app and deploy the full build output. See the playground configuration for a complete example. In the playground, add ?DEVTOOLS to the URL to show the devtools.

Development

pnpm run dev

Build and test

Build the package:

pnpm run build

Then test it on the playground (root folder):

pnpm run play # at root