|
| 1 | +# Polywrap Origin (0.11.0) |
| 2 | +## Features |
| 3 | +**`@polywrap/client-config-builder-js`:** |
| 4 | +* [PR-45](https://github.com/polywrap/javascript-client/pull/45) **Modular Config Bundles** |
| 5 | + * The `DefaultBundle` has been broken apart into two separate bundles: `sys` and `web3`. |
| 6 | + * `addBundle(...)` has been added to the `ClientConfigBuilder` interface. |
| 7 | + * `addDefaults()` now calls `addBundle("sys")` and `addBundle("web3")` internally. |
| 8 | + |
| 9 | +**`@polywrap/sys-config-bundle-js`:** |
| 10 | +* [PR-45](https://github.com/polywrap/javascript-client/pull/45) **Bundled System-Level Plugins & Resolvers** |
| 11 | + * The sys bundle includes: `logger`, `datetime`, `concurrent`, `http`, `httpResolver` |
| 12 | + * This package is compiled to run in both node.js and browsers. |
| 13 | + * In node.js, the bundle also includes: `fileSystem`, `fileSystemResolver`. |
| 14 | + |
| 15 | +**`@polywrap/web3-config-bundle-js`:** |
| 16 | +* [PR-45](https://github.com/polywrap/javascript-client/pull/45) **Bundled Web3 Plugins & Resolvers** |
| 17 | + * The web3 bundle includes: `ethereumProviderV1`, `ethereumProviderV2`, `ipfsHttpClient`, `ipfsResolver`, `ensTextRecordResolver`, `ensResolver`, `ensIpfsContenthashResolver`. |
| 18 | + |
| 19 | +**`@polywrap/config-bundle-types-js`:** |
| 20 | +* [PR-45](https://github.com/polywrap/javascript-client/pull/45) **Base Typings For Config Bundle Packages** |
| 21 | + * Valid config bundle packages are expected to export a `bundle` value, which is of type `Bundle`. |
| 22 | + |
| 23 | +## Breaking Changes |
| 24 | +**`@polywrap/client-config-builder-js`:** |
| 25 | +* [PR-47](https://github.com/polywrap/javascript-client/pull/47) **Renaming For Improved Accuracy** |
| 26 | + * Renamed `ClientConfigBuilder` to `PolywrapClientConfigBuilder` |
| 27 | + * Renamed `IClientConfigBuilder` to `ClientConfigBuilder` |
| 28 | + * Renamed `addWrapper(s)` to `setWrapper(s)` |
| 29 | + * Renamed `addPackage(s)` to `setPackage(s)` |
| 30 | + * Renamed `addRedirect(s)` to `setRedirect(s)` |
| 31 | + |
| 32 | +**`@polywrap/core-js`:** |
| 33 | +* [PR-32](https://github.com/polywrap/javascript-client/pull/32) **Rename `getEnvFromUriHistory` to `getEnvFromResolutionPath`** |
| 34 | + |
| 35 | +## Bugs |
| 36 | +**`@polywrap/client-js`** |
| 37 | +* [PR-32](https://github.com/polywrap/javascript-client/pull/32) **Improved Browser Compatability** |
| 38 | + * Building the JS client into browser-based applications no longer requires custom polyfills to remove Node.JS dependencies. |
| 39 | + |
| 40 | +**`@polywrap/client-cofig-builder-js`** |
| 41 | +* [PR-37](https://github.com/polywrap/javascript-client/pull/37) **Add `@polywrap/plugin-js` as a Dependency** |
| 42 | + * This resolves some package resolution warnings that are emitted from npm when installing the client-config-builder. |
| 43 | + |
| 44 | +**`@polywrap/wasm-js`:** |
| 45 | +* [PR-30](https://github.com/polywrap/javascript-client/pull/30) **Properly Serialize Empty Wrap Environment** |
| 46 | + * The wrap environment was being improperly encoded as an empty object, which had a size > 0 bytes, causing deserialization to fail. This has been fixed and it is now an empty byte array with size of 0. |
| 47 | + |
| 48 | +# Polywrap Origin (0.10.1) |
| 49 | +## Features |
| 50 | +**`@polywrap/wasm-js`:** |
| 51 | +* [PR-3](https://github.com/polywrap/javascript-client/pull/3) **WasmWrapper Subinvcations Now Retain The Resolution Context** |
| 52 | + * Added `resolutionContext` to the `WasmWrapper`'s state. |
| 53 | + * Pass the `resolutionContext` through to all subinvocations. |
| 54 | + |
| 55 | +## Bugs |
| 56 | +**`@polywrap/client-config-builder-js`** |
| 57 | +* [PR-8](https://github.com/polywrap/javascript-client/pull/8) **`tryResolveUri` Now Returns Wrap Packages** |
| 58 | + * The default resolver should not automatically convert packages to wrappers. Based on this, the `PackageToWrapperResolver` has been removed from the default config bundle. |
| 59 | + |
| 60 | +**`@polywrap/core-client-js`:** |
| 61 | +* [PR-3](https://github.com/polywrap/javascript-client/pull/3) **Properly Track Subinvocation Resolution Contexts** |
| 62 | + * Instead of passing the core resolution context to the resolution and invocation processes, seperate sub contexts are created for them. This means that subinvokes will now be tracked in the resolution context. |
| 63 | + |
| 64 | +**`@polywrap/plugin-js`:** |
| 65 | +* [PR-3](https://github.com/polywrap/javascript-client/pull/3) **Properly Track Subinvocation Resolution Contexts** |
| 66 | + * The client instance provided to plugin methods has been wrapped, enabling the automatic tracking of all subinvocation resolution contexts. |
| 67 | + |
1 | 68 | # Polywrap Origin (0.10.0) |
2 | 69 | ## Features |
3 | 70 | **`@polywrap/client-js`:** |
|
0 commit comments