@consenti/ui 0.4.0 → 0.5.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/react.d.cts CHANGED
@@ -622,6 +622,7 @@ declare class ConsentiSetup implements ConsentiWidgetAPI {
622
622
  private initializing;
623
623
  private profile;
624
624
  private resolvedBase;
625
+ private profilePatches;
625
626
  /** cookieId → Category lookup, rebuilt whenever `profile` changes. Avoids rescanning categories on every consent action. */
626
627
  private categoryIndex;
627
628
  /** Watchers created by the declarative `data-consenti-*` DOM scan — destroyed alongside the widget since they have no other owner. */
@@ -677,6 +678,14 @@ declare class ConsentiSetup implements ConsentiWidgetAPI {
677
678
  * cookies per compliance group (built-in or custom) without authoring a separate profile for
678
679
  * each one. Applied before `profileOverride`, which still always wins as the final catch-all. */
679
680
  private applyComplianceGroupOverride;
681
+ /**
682
+ * Applied in order: compliance-group override → `config.profileOverride` → each `setProfile()`
683
+ * patch. The `setProfile()` patches are kept as a list and replayed, not folded into one
684
+ * object, because folding runs `deepMerge` patch-onto-patch, which consumes `null`/`'*': null`
685
+ * delete markers before they ever reach the profile they were meant to delete from.
686
+ */
687
+ private applyProfileOverrides;
688
+ private warnIfAcceptOnly;
680
689
  /**
681
690
  * Whether `window.__tcfapi`/`window.__gpp` should stay uninstalled because the corresponding
682
691
  * server-side registration (`compliance.tcf`/`compliance.gpp`) is unconfirmed (cmpId/cmpVersion
package/dist/react.d.ts CHANGED
@@ -622,6 +622,7 @@ declare class ConsentiSetup implements ConsentiWidgetAPI {
622
622
  private initializing;
623
623
  private profile;
624
624
  private resolvedBase;
625
+ private profilePatches;
625
626
  /** cookieId → Category lookup, rebuilt whenever `profile` changes. Avoids rescanning categories on every consent action. */
626
627
  private categoryIndex;
627
628
  /** Watchers created by the declarative `data-consenti-*` DOM scan — destroyed alongside the widget since they have no other owner. */
@@ -677,6 +678,14 @@ declare class ConsentiSetup implements ConsentiWidgetAPI {
677
678
  * cookies per compliance group (built-in or custom) without authoring a separate profile for
678
679
  * each one. Applied before `profileOverride`, which still always wins as the final catch-all. */
679
680
  private applyComplianceGroupOverride;
681
+ /**
682
+ * Applied in order: compliance-group override → `config.profileOverride` → each `setProfile()`
683
+ * patch. The `setProfile()` patches are kept as a list and replayed, not folded into one
684
+ * object, because folding runs `deepMerge` patch-onto-patch, which consumes `null`/`'*': null`
685
+ * delete markers before they ever reach the profile they were meant to delete from.
686
+ */
687
+ private applyProfileOverrides;
688
+ private warnIfAcceptOnly;
680
689
  /**
681
690
  * Whether `window.__tcfapi`/`window.__gpp` should stay uninstalled because the corresponding
682
691
  * server-side registration (`compliance.tcf`/`compliance.gpp`) is unconfirmed (cmpId/cmpVersion
package/dist/vue.d.cts CHANGED
@@ -624,6 +624,7 @@ declare class ConsentiSetup implements ConsentiWidgetAPI {
624
624
  private initializing;
625
625
  private profile;
626
626
  private resolvedBase;
627
+ private profilePatches;
627
628
  /** cookieId → Category lookup, rebuilt whenever `profile` changes. Avoids rescanning categories on every consent action. */
628
629
  private categoryIndex;
629
630
  /** Watchers created by the declarative `data-consenti-*` DOM scan — destroyed alongside the widget since they have no other owner. */
@@ -679,6 +680,14 @@ declare class ConsentiSetup implements ConsentiWidgetAPI {
679
680
  * cookies per compliance group (built-in or custom) without authoring a separate profile for
680
681
  * each one. Applied before `profileOverride`, which still always wins as the final catch-all. */
681
682
  private applyComplianceGroupOverride;
683
+ /**
684
+ * Applied in order: compliance-group override → `config.profileOverride` → each `setProfile()`
685
+ * patch. The `setProfile()` patches are kept as a list and replayed, not folded into one
686
+ * object, because folding runs `deepMerge` patch-onto-patch, which consumes `null`/`'*': null`
687
+ * delete markers before they ever reach the profile they were meant to delete from.
688
+ */
689
+ private applyProfileOverrides;
690
+ private warnIfAcceptOnly;
682
691
  /**
683
692
  * Whether `window.__tcfapi`/`window.__gpp` should stay uninstalled because the corresponding
684
693
  * server-side registration (`compliance.tcf`/`compliance.gpp`) is unconfirmed (cmpId/cmpVersion
package/dist/vue.d.ts CHANGED
@@ -624,6 +624,7 @@ declare class ConsentiSetup implements ConsentiWidgetAPI {
624
624
  private initializing;
625
625
  private profile;
626
626
  private resolvedBase;
627
+ private profilePatches;
627
628
  /** cookieId → Category lookup, rebuilt whenever `profile` changes. Avoids rescanning categories on every consent action. */
628
629
  private categoryIndex;
629
630
  /** Watchers created by the declarative `data-consenti-*` DOM scan — destroyed alongside the widget since they have no other owner. */
@@ -679,6 +680,14 @@ declare class ConsentiSetup implements ConsentiWidgetAPI {
679
680
  * cookies per compliance group (built-in or custom) without authoring a separate profile for
680
681
  * each one. Applied before `profileOverride`, which still always wins as the final catch-all. */
681
682
  private applyComplianceGroupOverride;
683
+ /**
684
+ * Applied in order: compliance-group override → `config.profileOverride` → each `setProfile()`
685
+ * patch. The `setProfile()` patches are kept as a list and replayed, not folded into one
686
+ * object, because folding runs `deepMerge` patch-onto-patch, which consumes `null`/`'*': null`
687
+ * delete markers before they ever reach the profile they were meant to delete from.
688
+ */
689
+ private applyProfileOverrides;
690
+ private warnIfAcceptOnly;
682
691
  /**
683
692
  * Whether `window.__tcfapi`/`window.__gpp` should stay uninstalled because the corresponding
684
693
  * server-side registration (`compliance.tcf`/`compliance.gpp`) is unconfirmed (cmpId/cmpVersion
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@consenti/ui",
3
- "version": "0.4.0",
3
+ "version": "0.5.0",
4
4
  "description": "GDPR-style cookie consent widget — zero required runtime dependencies",
5
5
  "license": "Apache-2.0",
6
6
  "author": {
@@ -81,14 +81,14 @@
81
81
  "devDependencies": {
82
82
  "@consenti/types": "*",
83
83
  "@consenti/utils": "*",
84
- "@types/node": "^26.1.1",
85
- "@types/react": "^19.0.0",
84
+ "@types/node": "^26.1.2",
85
+ "@types/react": "^19.2.18",
86
86
  "sass": "^1.102.0",
87
87
  "tsup": "^8.5.0",
88
88
  "tsx": "^4.23.0",
89
89
  "typescript": "^6.0.3",
90
90
  "vite": "^8.2.0",
91
- "vue": "^3.5.40"
91
+ "vue": "^3.5.41"
92
92
  },
93
93
  "peerDependencies": {
94
94
  "react": ">=18.0.0",