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

@tulipes/cli

v0.1.1

Published

The tulipes command line: scaffold, sync, inspect, describe and run Tulipes apps

Readme

@tulipes/cli

The tulipes command line for Tulipes apps: scaffold, sync generated types, validate the environment, inspect routes, generate OpenAPI/Postman documents, run in watch mode, add modules and upgrade. It is separate from the runtime on purpose — a running app installs @tulipes/core alone, without this package, its templates or the TypeScript loader it carries.

npm install -g @tulipes/cli@next
tulipes init my-api            # minimal preset; --preset production for the full app
cd my-api && corepack enable && yarn install && yarn dev

Generated apps also list @tulipes/cli in devDependencies, so yarn dev, yarn sync, yarn spec and yarn tulipes new module <name> work without a global install and always match the app.

| Command | What it does | |---|---| | tulipes init [dir] [--minimal \| --preset minimal \| --preset production] [--no-queues] [--no-sockets] | scaffold an application; no services. The two opt-outs apply to the production preset and leave that provider, its files, dependencies and worker process out | | tulipes dev [entry] | regenerate types, then run under tsx watch | | tulipes sync | regenerate types/config.d.ts and .env.example | | tulipes env:check | validate the environment without booting | | tulipes routes [--offline \| --runtime] | list declared endpoints | | tulipes spec [--offline \| --runtime] [--openapi file] [--postman file] [--url base] | generate documents (needs @tulipes/spec in the app) | | tulipes new module <name> [--model\|--no-model] [--queues\|--no-queues] [--sockets\|--no-sockets] | scaffold a module for the providers the app declares | | tulipes update | upgrade the global CLI and, inside an app, its core and CLI ranges | | tulipes -v | print the CLI version, its bundled core, and the app's core when they differ |

Every command that touches an app boots or inspects it through the app's own @tulipes/core, so there is one copy of every framework singleton; the bundled core is only a fallback for directories with no install. Generated dependency ranges follow the core this CLI bundles.

Versions

0.1.1 bundles core 0.10.1 and scaffolds for it. See core's MIGRATING.md.