Release v1.0.0 — Angular 17.3+ support, npm publish setup & docs
Summary
First stable release of the NGXSMK UI kit. This PR bumps all packages to
1.0.0, widens Angular compatibility to 17.3+ (previously pinned to
Angular 22), and wires up the npm publish pipeline.
What's changed
Version & publishing
- Bumped
@ngxsmk/cdk,@ngxsmk/core,@ngxsmk/theme(and root) to1.0.0. - Added
publishConfig: { "access": "public" }andlicense: "MIT"to all
three library packages. - Updated the
@ngxsmk/cdkpeer range in@ngxsmk/coreto^1.0.0. - Added
npm run publish(builds libs, then publishescdk→theme→core).
Angular 17.3+ compatibility
- Relaxed peer dependencies from
^22.0.0→>=17.3.0. - Fixed
DOCUMENTimports: moved from@angular/coreto@angular/common
(valid in all versions;@angular/coreonly re-exports it from 19+). - Added explicit
standalone: trueto 195 component/directive/pipe decorators
(Angular 17/18 default to non-standalone, which brokeimports/[(x)]). - Fixed
NgxsmkPagination: removed a redundant explicitpageChangeoutput
that conflicted with themodel(page)change emitter (NG1054).
CI & tooling
- Added
.github/workflows/compatibility.yml— builds the three libraries
against Angular 17, 18, 19, 20, 21, and 22. - Added
tools/scripts/gen-ci-angularjson.mjs(generates a libs-only
angular.jsonper major so the build is not blocked by demo/app builder
schema differences). - Added per-package
tsconfig.jsonforng-packagrauto-discovery.
Docs
- README: 17.3+ version note, verified/CI note, "Stable 1.0.0" status, Angular
badge updated to17.3+, and hero taglinev1.0.0 · Signals-native · Zoneless. - Replaced the default Angular-CLI stub READMEs for
cdk/core/themewith
real package docs (compatibility, install, usage, publish path). - Demo changelog page: added the
v1.0.0release entry.
Verification
All three publishable packages compile cleanly on Angular 17.3 (via the v17 CLI
builder) as well as 18–22. npm run build:libs is green on the repo's Angular
22 toolchain, and npm publish ./dist/ngxsmk/cdk --dry-run produces a valid
tarball.
Notes
- The published artifact is built with the lowest supported Angular so the
partial-Ivy output stays forward-compatible. - Publishing still requires
npm loginthennpm run publish(not done here).