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

denisse

v0.0.1

Published

Denisse CLI — local development environment for Pascal projects, powered by Atlas Runtime.

Downloads

151

Readme

denisse

Denisse is a local development environment for Pascal projects that compile to TypeScript and run in the browser with Vite.

The CLI is the public product. Compilation, binding, and code generation are handled by the Atlas Engine (Atlas Runtime).

Experimental — Early development. Commands, config, and APIs may change.

Requirements

  • Node.js 18+ (20+ recommended)
  • npm

Install

npm install -g denisse

Or use without a global install:

npx denisse --version

Quick start

Create a new web project, install dependencies, and start the dev server:

denisse init my-app --template minimal
cd my-app
npm install
denisse run

Open the URL shown in the terminal (typically http://localhost:5173). Edit src/Main.pas — the page updates after rebuild.

Minimal config only

To add Denisse to an existing folder without scaffolding:

cd my-project
denisse init

This creates denisse.config.json. Add Pascal sources under src/ and run denisse build.

Commands

| Command | Description | |---------|-------------| | denisse init [name] | Create denisse.config.json or scaffold a full project | | denisse run / denisse dev | Build and start the target dev server | | denisse build | Compile Pascal → src/generated/ | | denisse compile <file.pas> | Compile a single .pas file to TypeScript | | denisse doctor | Check Node, npm, and project setup | | denisse --version | Show CLI version | | denisse --help | Show usage |

Init options

denisse init my-app --template minimal   # welcome page + Main.pas (default)
denisse init my-app --template app       # multi-unit (Main + App)
denisse init my-app -d ./projects/my-app # custom directory

Project layout

A scaffolded web project looks like this:

my-app/
  denisse.config.json   # project contract
  package.json
  index.html
  src/
    Main.pas            # your Pascal code
    main.ts             # Vite entry (imports generated code)
    generated/          # output only — do not edit

Denisse never modifies your Pascal sources. Generated TypeScript is written only to outDir (default src/generated/).

Configuration

denisse.config.json is the project contract:

{
  "runtime": "atlas",
  "version": "0.0.1",
  "name": "my-app",
  "target": "web",
  "profile": "web",
  "sourceDir": "src",
  "outDir": "src/generated",
  "entry": "Main.pas"
}

| Field | Default | Description | |-------|---------|-------------| | runtime | atlas | Engine runtime | | name | — | Project name (required for builds) | | target | web | Output target | | profile | web | Language profile | | sourceDir | src | Pascal source directory | | outDir | src/generated | Generated TypeScript output | | entry | Main.pas | Main unit |

Legacy atlas.json is still read for backward compatibility.

Typical package.json scripts

{
  "scripts": {
    "postinstall": "denisse build",
    "dev": "denisse build && vite",
    "preview": "vite preview"
  },
  "devDependencies": {
    "denisse": "^0.0.1",
    "vite": "^6.3.5",
    "typescript": "^5.8.3"
  }
}

postinstall generates src/generated/ on npm install. dev rebuilds Pascal before starting Vite.

Product vs engine

| Layer | Name | |-------|------| | CLI, npm, developer experience | Denisse | | Compiler, binder, IR, codegen | Atlas (@denisse-dev/compiler, Atlas Runtime) |

Denisse CLI → Atlas Runtime → Atlas Engine → generated TypeScript → Vite

Troubleshooting

| Problem | Fix | |---------|-----| | denisse not found | Use npx denisse or npm install -g denisse | | Blank page in browser | Run npm install or denisse build to generate src/generated/ | | Failed to resolve ./generated/Main.js | Run denisse build in the project directory | | .pas changes not visible | Restart npm run dev or save to trigger rebuild |

Run denisse doctor for a quick environment check.

Links

License

MIT