Workspace of @lenne.tech/ng-base, the Angular library of the lenne.Tech stack
(Angular 22, Tailwind CSS 4, Spartan UI, nest-server integration). Template for apps:
ng-base-starter.
| Path | Content |
|---|---|
projects/ng-base/ |
The library (primary entry point plus auth, ui, files, share, ai, sync, server, testing, utils) |
projects/playground/ |
SSR app for library E2E tests against a local nest-server-starter (API :3000, app :3001) |
scripts/ |
check, version sync, package manifest and publish workflow checks, Angular baseline check, Spartan helm generator |
migration-guides/ |
Migration guide for every MINOR release (and the 18.x → 22.0.0 rebuild) |
pnpm install
pnpm test # unit tests (Vitest)
pnpm build # library → dist/ng-base
pnpm dev # playground on http://localhost:3001 (API proxy → http://localhost:3000)
pnpm test:e2e # playground E2E (needs nest-server-starter on :3000)
NG_BASE_E2E_AUTH_MODE=jwt pnpm test:e2e # the same in nest-server's real JWT mode (cookies: false)
pnpm run check # full gate with auto-fix (check:raw = read-only)
pnpm run check:baseline # compare the workspace with a fresh Angular CLI scaffold (release gate, after ng update)Test a change in an app (e.g. ng-base-starter): pnpm build, then in the app
"@lenne.tech/ng-base": "file:../ng-base/dist/ng-base" with "dependenciesMeta": { "@lenne.tech/ng-base": { "injected": true } }
and pnpm install after every ng-base build. Not pnpm link: the symlinked package resolves @angular/core from this
workspace, two copies end up in the app and SSR fails with NG0203.
MAJOR.MINOR.PATCH, the scheme every lenne.Tech base repository uses (modelled on @lenne.tech/nest-server):
| Part | Meaning |
|---|---|
MAJOR |
The Angular major (22.x.x = Angular 22). It moves only with Angular, never because a change is breaking. |
MINOR |
A change an app has to act on when it updates (behaviour, code or configuration), always with a guide in migration-guides/. |
PATCH |
A fix, improvement or addition an app takes over without doing anything. |
ng-base-starter always carries the version of the ng-base it pins: every ng-base release is followed by a starter
release with the same number. ng-base skips 22.0.3, which the starter released before this rule; from 22.0.4 on both
share every version number.
Bump the version in package.json, run pnpm run version:sync, update CHANGELOG.md (and add the migration guide for
a MINOR release), commit, create the annotated tag v<version> and push it. The publish workflow runs the gate and
publishes dist/ng-base to npm through Trusted Publishing (OIDC, Trusted Publisher on npmjs.com: lenneTech /
ng-base / publish.yml, no environment) with provenance, without any npm token (since 22.0.4).
MIT, © lenne.Tech GmbH