I wanted to create a simple mithril.js app but then was heavily influenced by @mpnpm and I wanted to use Miniflare and integration tests.
pnpm i
You can then cd into different packages (mainly api and app). While you can execute commands from root, it is just best to cd into the directories you are working within. Look at pnpm filtering to understand and better leverage workspace executions from different locations.
Every package has the following commands:
pnpm dev Starts development in watch mode
pnpm build Runs a production build
This directory contains build specific packages, they are:
This is a shareable tsconfig.json that each package that is TypeScript based can extend upon. It includes just some basic defaults.
This is a shareable Prettier config. Extend configuration from within package.json files, eg:
{
"prettier": "@mpnpm/prettier-config"
}This directory contains non-build specific packages, those which would be a library, application, module or something else. Contained within this example is the following:
This is a simple Cloudflare Worker generated from the TypeScript template
This is a basic mithril app that uses @mpnpm/api and is bundling using Rollup and TypeScript. It demonstrates a private package using workspace packages.