01
Use the scoped initializer
Published Nexis packages are hosted on GitHub Packages. Configure the @mohammedaydan scope when required, then use the current scoped initializer and commit the generated lockfile.
02
Keep the generated shape
A standard project uses src/routes for pages, public for assets, an HTML shell with Nexis outlets, TypeScript configuration, and package scripts that call the Nexis CLI.
03
Verify immediately
Run the production build and project checks before adding deployment logic. A broken build can omit route HTML, chunks, or asset metadata.
npm config set @mohammedaydan:registry https://npm.pkg.github.com
pnpm dlx @mohammedaydan/create-nexis@latest my-nexis-app --yes --ts
cd my-nexis-app
pnpm install
pnpm devPRACTICAL LABS
Run this capability.
Each example states the observable output, the boundary that remains your responsibility, and the check that proves the result.
01
Create an interactive TypeScript project
Shellpnpm dlx @mohammedaydan/create-nexis@1.3.3 my-nexis-app --yes --ts --template interactive
cd my-nexis-app
pnpm install
pnpm dev- OUTPUT
- A Nexis project with an HTML shell, routes, and verification scripts.
- BOUNDARY
- Configure package access in user or CI configuration; never commit a registry token.
- PROVE IT
- Run pnpm typecheck && pnpm check before editing the scaffold.
VERIFICATION
Prove the contract.
Run pnpm build and the available typecheck, lint, and test scripts before changing the generated scaffold.