Skip to content

feat: scaffold template-lib-angular as a single Angular library project - #8

Closed
NoNamer777 wants to merge 4 commits into
mainfrom
feat/scaffold-angular-library
Closed

feat: scaffold template-lib-angular as a single Angular library project#8
NoNamer777 wants to merge 4 commits into
mainfrom
feat/scaffold-angular-library

Conversation

@NoNamer777

Copy link
Copy Markdown
Member

Summary

Restructure this repo from the template-app-angular application clone into a library-only workspace, per the "Angular Library Template" map's destination:

  • Ran ng generate library to scaffold @dnd-mapp/template-lib-angular under projects/
  • Gave the library's public API one placeholder function (add) and its test, demonstrating the export surface
  • Removed the app-specific bootstrap (src/main.ts, src/index.html, src/core/**) and the now-orphaned tsconfig.app.json/tsconfig.spec.json
  • Dropped the app project from angular.json, and wired the library's test target to match the repo's existing vitest/coverage conventions (the schematic's default was bare-bones)

Out of scope here: Docker, SSL dev server, Playwright e2e, and src/design-system/ removal. Those belong to "Remove app-runtime scaffolding".

Related issues

Resolves #2

Checklist

  • Title and description follow the Creating a Pull Request guide
  • Commit messages follow Conventional Commits and are grouped by intent
  • Tests were added or updated as needed
  • Documentation was updated as needed
  • CI checks pass

Restructure the repo from the template-app-angular application clone
into a library-only workspace: generate the library under projects/,
drop the app project and its bootstrap (main.ts, index.html, src/core),
and wire the library's build/test/lint targets to angular.json/tsconfig.
ng generate library added both as ad-hoc devDependencies. jsdom is
unused since this repo tests in a real browser via vitest/playwright,
and ng-packagr belongs in the shared pnpm catalog like every other
Angular tooling dependency.
Nothing in this workspace imports the library by package name, only
the schematic-added mapping did. Drop it rather than carry dead config.
Drop the redundant ts-check pragma and tsconfig doc-link comments the
schematic adds, and reformat public-api.ts's docblock and the
tsconfig key ordering to match this repo's conventions.
@NoNamer777 NoNamer777 closed this Aug 13, 2026
@NoNamer777
NoNamer777 deleted the feat/scaffold-angular-library branch August 13, 2026 08:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Scaffold the Angular library project

1 participant