JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 128
  • Score
    100M100P100Q57389F
  • License ISC

🌹 CLI for creating web projects with (my) sensible defaults

Package Exports

  • create-krispya
  • create-krispya/dist/index.mjs

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (create-krispya) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

create-krispya

Full AI generated docs can be found here.

A CLI for scaffolding modern, clutter-free web projects.

Quick Start

pnpm create krispya
# or
bun create krispya
# or
npm create krispya@latest
# and follow the prompts

Who cares?

I really hate looking at my repo when there are 20 config files sitting in root. It is noisy and, worst of all, plain ugly. Not only do we derserve beautiful code, but in the post-AI world great taste is all I have. In pursuit of minimalism, as many files as possible are moved to hidden directories such as .config and.vscode.

We are also in a time of rampant changes to the JS toolchain ecossytem. In an effort to keep up, but also encourage trying new tools out, I wante to build a framework that let me swap between them with some guardrails.

Current Status

Consider this experimental but safe. It was vibe coded and then I decided this project deserved better so I am going through it piece by piece and making it whole and loved.

Single-project workspaces

The basic dish.