Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/wild-papayas-judge.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
'@tanstack/devtools': patch
---

Add inertia 3 devtool to registry
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟑 Minor

Polish release note wording for consistency.

Use product casing/plural form to match existing terminology: β€œAdd Inertia 3 devtools plugin to the registry”.

πŸ€– Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.changeset/wild-papayas-judge.md at line 5, Update the release note text
that currently reads "Add inertia 3 devtool to registry" to the consistent
product-cased and pluralized phrasing "Add Inertia 3 devtools plugin to the
registry" so it matches existing terminology and casing conventions.

21 changes: 21 additions & 0 deletions packages/devtools/src/tabs/plugin-registry.ts
Original file line number Diff line number Diff line change
Expand Up @@ -259,6 +259,27 @@ const PLUGIN_REGISTRY: Record<string, PluginMetadata> = {
isNew: true,
tags: ['Router', 'Prefetch', 'Analytics', 'Overlay', 'TanStack'],
},

// Santos Vilanculos β€” Inertia 3 Devtools for React
'@santosvilanculos/bevor-react': {
packageName: '@santosvilanculos/bevor-react',
title: 'Inertia 3 Devtools',
description: 'Inertia 3 devtools built on top of TanStack DevTools',
pluginImport: {
importName: 'inertiaDevtoolsPlugin',
type: 'function',
},
pluginId: 'inertia-devtools',
logoUrl:
'https://raw.githubusercontent.com/santosvilanculos/bevor/main/logo.png',
docsUrl:
'https://github.com/SantosVilanculos/bevor/tree/main/packages/react',
repoUrl: 'https://github.com/SantosVilanculos/bevor',
author: 'Santos Vilanculos (santosvilanculos@yahoo.com)',
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Remove direct email address from public plugin metadata.

Committing a personal email in author introduces unnecessary PII exposure in published artifacts. Prefer name/handle only.

πŸ”§ Suggested change
-    author: 'Santos Vilanculos (santosvilanculos@yahoo.com)',
+    author: 'Santos Vilanculos (`@SantosVilanculos`)',
πŸ“ Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
author: 'Santos Vilanculos (santosvilanculos@yahoo.com)',
author: 'Santos Vilanculos (`@SantosVilanculos`)',
πŸ€– Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@packages/devtools/src/tabs/plugin-registry.ts` at line 278, The plugin
metadata currently contains a personal email in the author field ("author:
'Santos Vilanculos (santosvilanculos@yahoo.com)')"); remove the direct email and
leave only a name or handle (e.g., "Santos Vilanculos" or "santosvilanculos") in
the author value in packages/devtools/src/tabs/plugin-registry.ts (the author
metadata entry) to avoid publishing PII; update any other occurrences of the
same author string in the file if present and run tests/build to verify no
metadata consumers rely on the email.

framework: 'react',
isNew: true,
tags: ['TanStack', 'React', 'Inertia', 'Laravel'],
},
}

/**
Expand Down