@s-libs/app-state - npm Package Compare versions

Comparing version 16.1.0 to 17.0.0-next.0

lib/utils/persistent-store.d.ts

@@ -38,3 +38,3 @@ import { MigrationManager, VersionedObject } from '@s-libs/js-core';
  *
- * Later when you want to change the schema of the state, it's time to take advantage of the `{@link MigrationManager}:
+ * At this point, if you change `_version` the store will be reset to the default state. This is a convenience during initial development of your app. Once it is released to real users, you will want to use a {@link MigrationManager} to avoid wiping out your users' data:
  *
@@ -41,0 +41,0 @@ * ```ts

package.json

 {
   "name": "@s-libs/app-state",
-  "version": "16.1.0",
+  "version": "17.0.0-next.0",
   "author": "Simonton Software",
@@ -13,5 +13,5 @@ "license": "MIT",
   "peerDependencies": {
-    "@s-libs/js-core": "^16.1.0",
-    "@s-libs/micro-dash": "^16.1.0",
-    "@s-libs/rxjs-core": "^16.1.0"
+    "@s-libs/js-core": "^17.0.0-next.0",
+    "@s-libs/micro-dash": "^17.0.0-next.0",
+    "@s-libs/rxjs-core": "^17.0.0-next.0"
   },
@@ -18,0 +18,0 @@ "dependencies": {

New alerts

No v1

Quality

Package is not semver >=1. This means it is not stable and does not support ^ ranges.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

167600

increased by0.52%

Lines of code

1669

increased by1.21%

Worsened metrics

Number of low quality alerts

2

increased by100%

No dependency changes