anchordb 1.0.1 → 1.0.3
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/CHANGELOG.md +42 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,48 @@ All notable changes to the `anchordb` packages.
|
|
|
5
5
|
This project follows [semantic versioning](https://semver.org/). While the version is `0.x`, minor
|
|
6
6
|
releases may contain breaking changes.
|
|
7
7
|
|
|
8
|
+
## 1.0.3
|
|
9
|
+
|
|
10
|
+
Guidance fix for Expo apps. No change to database behaviour.
|
|
11
|
+
|
|
12
|
+
- **`createAnchorDB` and the `anchordb-react` README recommended `npx expo install --fix`**, which
|
|
13
|
+
cannot help: it only realigns packages listed in the package.json of the app, and `expo-sqlite`
|
|
14
|
+
and `react-native-get-random-values` arrive through `anchordb-react`. Both now name
|
|
15
|
+
`npx expo install expo-sqlite react-native-get-random-values`, which pins the drivers at the top
|
|
16
|
+
level where the wide ranges from 1.0.2 dedupe onto them.
|
|
17
|
+
- Verified in an Expo SDK 56 app: with the pins, both drivers resolve to the versions the SDK pins
|
|
18
|
+
(`expo-sqlite` 56.0.6, `react-native-get-random-values` 1.11.0), deduped, and
|
|
19
|
+
`npx expo install --check` reports dependencies up to date. Without the pin the polyfill resolves
|
|
20
|
+
to 2.0.0 against the 1.11 native module Expo Go ships.
|
|
21
|
+
|
|
22
|
+
## 1.0.2
|
|
23
|
+
|
|
24
|
+
`anchordb-react` pinned its native drivers to a single Expo SDK.
|
|
25
|
+
|
|
26
|
+
- **`expo-sqlite` was declared `^57.0.3`**, so an app on Expo SDK 56 (`expo-sqlite ~56.0.4`) could
|
|
27
|
+
not dedupe it. npm nested a second, SDK 57 `expo-sqlite` whose JavaScript no longer matched the
|
|
28
|
+
native build of the app. The intended range was `>=14`; `npm install -w` rewrote it with a caret
|
|
29
|
+
when the dependency was added. Both drivers now take wide ranges (`expo-sqlite >=14`,
|
|
30
|
+
`react-native-get-random-values >=1.11`), so npm reuses whatever version the Expo SDK of the app
|
|
31
|
+
already installed.
|
|
32
|
+
- A test now asserts both ranges accept the drivers Expo SDK 56 and 57 ship and are not caret- or
|
|
33
|
+
tilde-pinned, so a future `npm install -w` cannot silently narrow them again.
|
|
34
|
+
|
|
35
|
+
Found by comparing against a working Expo SDK 56 app on the same machine.
|
|
36
|
+
|
|
37
|
+
## 1.0.1
|
|
38
|
+
|
|
39
|
+
Two defects in `anchordb-angular`, both in its *documented* usage, found by building a real Ionic
|
|
40
|
+
app against the published package for the first time.
|
|
41
|
+
|
|
42
|
+
- **The provider arrays did not typecheck against Angular.** `Provider.useFactory` was declared
|
|
43
|
+
optional, so the array was not assignable to Angular’s `Provider[]` and the documented
|
|
44
|
+
`bootstrapApplication` example failed to compile. It is now required, matching what every
|
|
45
|
+
provider in the package actually returns, and `useValue` — declared but never used — is gone.
|
|
46
|
+
- **`.toObservable()` was documented but implemented nowhere.** The real API is
|
|
47
|
+
`AnchorService.find$` / `findOne$` / `count$`, which return an RxJS-interop `AnchorObservable`
|
|
48
|
+
the `async` pipe accepts directly. The documentation now shows that.
|
|
49
|
+
|
|
8
50
|
## 1.0.0
|
|
9
51
|
|
|
10
52
|
**Versioning changes with this release.** The major version now tracks the React / Angular major the
|