@typewirets/core 0.2.0-rc.1 → 0.2.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/CHANGELOG.md +5 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
-
## 0.2.0
|
|
3
|
+
## 0.2.0
|
|
4
4
|
|
|
5
5
|
- **New: `container.preload(opts?)` creates singletons ahead of time,** so they can be read with `getInstanceSync` afterwards. Without options it creates every singleton bound at the time of the call; with `{ wires }`, only those wires and their imports. Creations run in parallel, wires that aren't singletons are skipped, and values already created are kept, so a later call creates only what is new. A failure rejects with that creation's own error, and the other creations still finish and are cached. New type: `PreloadOpts`. See "Preloading" in the README.
|
|
6
6
|
- **`container.getAllAsync()` is deprecated** in favour of `preload`. It resolves bindings one at a time and also creates a value for every transient binding. It still works.
|
|
@@ -24,6 +24,10 @@ Fixes three singleton-cache behaviours that diverged from the typewire contract
|
|
|
24
24
|
- `bind` must replace an existing binding for the same type, because `apply` no longer unbinds first. Its return type is now `void | Promise<void>`, and `apply` awaits it.
|
|
25
25
|
- The Inversify adapter's `bind` now does the unbind itself, so its behaviour is unchanged: re-applying still discards Inversify's cached instance.
|
|
26
26
|
|
|
27
|
+
## 0.2.0-rc.1
|
|
28
|
+
|
|
29
|
+
Release candidate for 0.2.0, with the same changes. They are listed under 0.2.0.
|
|
30
|
+
|
|
27
31
|
## 0.1.0
|
|
28
32
|
|
|
29
33
|
- Initial release.
|