Skip to content

docs(plugin-directory): add zustand-devtools and navigation-inspector plugins#291

Merged
V3RON merged 1 commit into
callstackincubator:mainfrom
IronTony:feat/add-irontony-plugins
May 28, 2026
Merged

docs(plugin-directory): add zustand-devtools and navigation-inspector plugins#291
V3RON merged 1 commit into
callstackincubator:mainfrom
IronTony:feat/add-irontony-plugins

Conversation

@IronTony
Copy link
Copy Markdown
Contributor

Description

Adds two community Rozenite plugins to the plugin directory:

Both entries were appended to plugin-directory.json with the standard npmUrl + githubUrl fields. Both packages are published on npm and both repositories are public.

Related Issue

N/A, this follows the documented "open a pull request to contribute your plugin to this list" flow on the plugin directory page. Happy to open a tracking issue first if maintainers prefer.

Context

plugin-directory.json is the source of truth for the directory; all other metadata (version, description, star count, official badge) is resolved at build time from the npm registry and GitHub API, so no extra fields are needed. Both plugins are community-scoped (not @rozenite/), so they render with isOfficial=false, consistent with existing community entries like rozenite-growthbook-plugin and zorro. GitHub URLs point to the repo roots, matching the convention for standalone community repos.

Testing

  • Validated plugin-directory.json parses cleanly (node -e "JSON.parse(...)"), no trailing-comma or syntax errors.
  • Confirmed both npm package URLs resolve (rozenite-zustand-devtools v1.0.2, rozenite-navigation-inspector v1.1.1) and both GitHub repos are public.
  • Verified the diff touches only plugin-directory.json (8 lines added).

@V3RON V3RON merged commit 46013e7 into callstackincubator:main May 28, 2026
1 check passed
draggie pushed a commit to draggie/rozenite that referenced this pull request Jun 2, 2026
… plugins (callstackincubator#291)

## Description

Adds two community Rozenite plugins to the plugin directory:

- **rozenite-zustand-devtools**: DevTools plugin for inspecting Zustand
store state in React Native apps
(https://github.com/IronTony/rozenite-zustand-devtools)
- **rozenite-navigation-inspector**: DevTools plugin for inspecting
navigation state in Expo Router / React Navigation apps
(https://github.com/IronTony/rozenite-navigation-inspector)

Both entries were appended to `plugin-directory.json` with the standard
`npmUrl` + `githubUrl` fields. Both packages are published on npm and
both repositories are public.

## Related Issue

N/A, this follows the documented "open a pull request to contribute your
plugin to this list" flow on the plugin directory page. Happy to open a
tracking issue first if maintainers prefer.

## Context

`plugin-directory.json` is the source of truth for the directory; all
other metadata (version, description, star count, official badge) is
resolved at build time from the npm registry and GitHub API, so no extra
fields are needed. Both plugins are community-scoped (not `@rozenite/`),
so they render with `isOfficial=false`, consistent with existing
community entries like `rozenite-growthbook-plugin` and `zorro`. GitHub
URLs point to the repo roots, matching the convention for standalone
community repos.

## Testing

- Validated `plugin-directory.json` parses cleanly (`node -e
"JSON.parse(...)"`), no trailing-comma or syntax errors.
- Confirmed both npm package URLs resolve (rozenite-zustand-devtools
v1.0.2, rozenite-navigation-inspector v1.1.1) and both GitHub repos are
public.
- Verified the diff touches only `plugin-directory.json` (8 lines
added).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants