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

@shiva-fw/api

v1.0.0

Published

External standalone API server for the Shiva FiveM framework

Readme

shiva-api

External standalone API server for the Shiva FiveM framework. Provides REST endpoints, real-time WebSocket broadcasting, and a bridge between shiva-core (FiveM) and external consumers like admin panels, Discord bots, and mobile apps.

Requirements

  • Node.js 18+
  • A running shiva-core instance (for bridge connection)

Getting Started

cp .env.example .env   # fill in your values
npm install
npm run dev

The server starts on http://localhost:3000 by default. The FiveM bridge will retry automatically until shiva-core is available.

Configuration

See .env.example for all options. Key variables:

| Variable | Default | Description | |---|---|---| | PORT | 3000 | HTTP server port | | FIVEM_WS_URL | ws://localhost:30120/shiva | FiveM bridge URL (internal only) | | API_SECRET | — | JWT signing secret | | DISCORD_CLIENT_ID | — | Discord OAuth2 app ID | | DISCORD_CLIENT_SECRET | — | Discord OAuth2 app secret | | BROADCAST_DRIVER | websocket | Broadcasting driver (websocket, reverb, pusher, socketio) |

Scripts

npm run dev        # start with file watching
npm start          # production start
npm test           # run Jest tests with coverage
npm run lint       # ESLint

Docker

docker compose up -d

Requires a fivem Docker network (docker network create fivem). See compose.yml for all options.

Architecture

┌──────────────┐     WebSocket      ┌──────────────┐     REST/WS     ┌──────────────┐
│  FiveM       │◄──────────────────►│  shiva-api   │◄──────────────►│  shiva-panel │
│  shiva-core  │   (internal only)   │  (this repo) │   (external)   │  Discord bot │
└──────────────┘                    └──────────────┘                └──────────────┘

The bridge WebSocket (FIVEM_WS_URL) is internal — never expose it to the internet. All game data flows through the bridge; this server never touches the database directly.

Related Repositories

| Repo | Purpose | |---|---| | shiva | FiveM Docker boilerplate | | shiva-fw | Shared Lua foundation | | shiva-core | FiveM framework engine | | shiva-modules | 71 default RP modules | | shiva-db | Database layer | | shiva-cli | Developer CLI | | shiva-boot | Boot utilities | | shiva-test | Testing framework | | shiva-docs | Documentation |