What? My debouncer can have dedicated devtools? Yep!
TanStack Pacer ships devtools for watching and debugging every registered utility in real time. They run as a plugin inside the TanStack Devtools multi-panel UI.
Note
The devtools are excluded from production builds by default, so they add nothing to your production bundle. See Production builds if you need them in production.
Install the devtools packages for your framework:
npm install @tanstack/react-devtools @tanstack/react-pacer-devtoolsnpm install @tanstack/solid-devtools @tanstack/solid-pacer-devtoolsComing soon...
import { TanStackDevtools } from '@tanstack/react-devtools'
import { pacerDevtoolsPlugin } from '@tanstack/react-pacer-devtools'
function App() {
return (
<div>
{/* Your app content */}
<TanStackDevtools
eventBusConfig={{
debug: false,
}}
plugins={[pacerDevtoolsPlugin()]}
/>
</div>
)
}import { TanStackDevtools } from '@tanstack/solid-devtools'
import { pacerDevtoolsPlugin } from '@tanstack/solid-pacer-devtools'
function App() {
return (
<div>
{/* Your app content */}
<TanStackDevtools
eventBusConfig={{
debug: false,
}}
plugins={[pacerDevtoolsPlugin()]}
/>
</div>
)
}The default imports become no-ops in production builds:
// This is a no-op in production builds
import { pacerDevtoolsPlugin } from '@tanstack/react-pacer-devtools'To debug a production issue with full devtools, switch to the production-specific imports:
// This includes full devtools even in production builds
import { pacerDevtoolsPlugin } from '@tanstack/react-pacer-devtools/production'A utility only registers with the devtools when you give it a key. Leave the option out and the instance stays out of the panels.
const debouncer = new Debouncer(myDebounceFn, {
key: 'My Debouncer', // friendly name shown in the devtools
wait: 1000,
})