@aegov/designsystem-angular 0.2.25 → 4.0.0

package/package.json

@@ -1,10 +1,10 @@
 {
   "name": "@aegov/designsystem-angular",
-  "version": "0.2.25",
+  "version": "4.0.0",
   "peerDependencies": {
     "@angular/common": ">=18.0.0",
     "@angular/core": ">=18.0.0",
-    "@aegov/designsystem": "*"
+    "@aegov/designsystem": "^4.0.0"
   },
   "dependencies": {
     "tslib": "^2.3.0"
@@ -22,6 +22,10 @@
     ".": {
       "types": "./types/aegov-designsystem-angular.d.ts",
       "default": "./fesm2022/aegov-designsystem-angular.mjs"
+    },
+    "./provider": {
+      "types": "./types/aegov-designsystem-angular-provider.d.ts",
+      "default": "./fesm2022/aegov-designsystem-angular-provider.mjs"
     }
   },
   "type": "module"

package/types/aegov-designsystem-angular-provider.d.ts

@@ -0,0 +1,23 @@
+import { EnvironmentProviders } from '@angular/core';
+
+/**
+ * Registers every `aegov-*` element through the lazy loader and runs the design
+ * system's global script (toast live region, `window.aegovToast`).
+ *
+ * Add it to the application's providers (`bootstrapApplication`, or the root
+ * NgModule's `providers`). It must be an application-level provider: Angular only
+ * runs `APP_INITIALIZER` from the root environment injector.
+ *
+ * The loader is imported dynamically so apps that never call this function don't
+ * bundle it (the loader is a side-effect module). It lives in this secondary entry
+ * point because a bundler emits the loader's lazy chunks for any `import()` in a
+ * module it includes, even inside a function the app never calls: an app that
+ * imports only wrappers from `@aegov/designsystem-angular` would otherwise ship
+ * ~70 unused chunk files.
+ *
+ * This is what `provideAppInitializer()` expands to; the token form is used so the
+ * package keeps working on Angular 18, which has no `provideAppInitializer()`.
+ */
+declare function provideDesignSystem(): EnvironmentProviders;
+
+export { provideDesignSystem };