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

@plyaz/store

v1.1.3

Published

State management package for Plyaz platform using Zustand and React Query.

Downloads

541

Readme

📦 Plyaz Package Template

This is the official state management package for the Plyaz platform. It defines our unified state architecture using Zustand for global client state and React Query for server state, ensuring clean separation of concerns, high performance, and an excellent developer experience.

Use this package to manage global, shared, and API-driven states across all Plyaz applications.

🚀 Getting Started

🌀 Option 1: Use GitHub Template

  1. Go to @plyaz/store.

  2. Clone the repo:

   git clone https://github.com/Plyaz-Official/store.git @plyaz/store
   cd @plyaz/store
   pnpm install

📦 Project Structure

@plyaz/store/
├── src/
│   ├── index.ts              # Main exports
│   ├── middleware/           # Custom middleware
│   ├── utils/                # Utility functions
│   └── slices/               # Domain-specific stores (These are only example)
│       ├── auth.ts           # Authentication state
│       ├── user.ts           # User profile & preferences
│       ├── wallet.ts         # Wallet connections & balances
│       ├── transactions.ts   # Transaction history & status
│       └── notifications.ts  # User notifications

📜 Scripts & Commands

{
    "build": "tsup",
    "dev": "tsup --watch",
    "test": "vitest"
}

🔁 Dev Workflow

Local Linking (for active development) In the package repo: pnpm build pnpm link --global

In a consumer repo (e.g. frontend app):

pnpm link --global @plyaz/store

Publishing to GitHub Packages

Ensure .npmrc in your user root exists:

@plyaz:registry=https://npm.pkg.github.com/ //npm.pkg.github.com/:_authToken=${GITHUB_TOKEN}

Then publish:

pnpm publish --access=restricted

Best Practices

Use Zustand for UI/global state management (client-side) Use React Query for server-side API state (fetch, cache, revalidation) Keep slices modular (e.g., useAuthStore, useUIStore) Always export from src/index.ts Never mix API logic inside Zustand stores Include unit tests for every slice and query Use @plyaz/devtools for linting, testing, and build consistency Maintain separation between client and server state domains

How to add slice in @plyaz/store

Create a slice in /slices/. Add its type in @plyaz/types in RootStore type . Update Store to include the new slice.

Shared Tooling

This package is pre-integrated with: TypeScript (strict mode) Zustand (for global client state) React Query (for server state) ESLint & Prettier via @plyaz/devtools Vitest (for testing) CI-ready for GitHub Actions

When to Use @plyaz/store

Use @plyaz/store when your project needs: Shared global state (e.g., UI toggles, auth session, modals) Cached API state (e.g., user profile, settings, dashboard data) Seamless syncing between local state and remote data A consistent state layer across all Plyaz apps