Polywrap Origin (0.11.0)
Polywrap Origin (0.11.0)
Features
@polywrap/core-js
:
- PR-6 Improved URI Inference
- Non-wrap URI schemes can now be used (ex:
https://domain.com/path
). The non-wrap scheme will be used as the authority, and all other contents will be shifted into the path. - Examples:
https://domain.com/path
intowrap://https/domain.com/path
ipfs://QmHASH
intowrap://ipfs/QmHASH
- Non-wrap URI schemes can now be used (ex:
@polywrap/client-config-builder-js
:
- PR-45 Modular Config Bundles
- The
DefaultBundle
has been broken apart into two separate bundles:sys
andweb3
. addBundle(...)
has been added to theClientConfigBuilder
interface.addDefaults()
now callsaddBundle("sys")
andaddBundle("web3")
internally.
- The
@polywrap/sys-config-bundle-js
:
- PR-45 Bundled System-Level Plugins & Resolvers
- The sys bundle includes:
logger
,datetime
,concurrent
,http
,httpResolver
- This package is compiled to run in both node.js and browsers.
- In node.js, the bundle also includes:
fileSystem
,fileSystemResolver
.
- The sys bundle includes:
@polywrap/web3-config-bundle-js
:
- PR-45 Bundled Web3 Plugins & Resolvers
- The web3 bundle includes:
ethereumProviderV1
,ethereumProviderV2
,ipfsHttpClient
,ipfsResolver
,ensTextRecordResolver
,ensResolver
,ensIpfsContenthashResolver
.
- The web3 bundle includes:
@polywrap/config-bundle-types-js
:
- PR-45 Base Typings For Config Bundle Packages
- Valid config bundle packages are expected to export a
bundle
value, which is of typeBundle
.
- Valid config bundle packages are expected to export a
Breaking Changes
@polywrap/client-config-builder-js
:
- PR-47 Renaming For Improved Accuracy
- Renamed
ClientConfigBuilder
toPolywrapClientConfigBuilder
- Renamed
IClientConfigBuilder
toClientConfigBuilder
- Renamed
addWrapper(s)
tosetWrapper(s)
- Renamed
addPackage(s)
tosetPackage(s)
- Renamed
addRedirect(s)
tosetRedirect(s)
- Renamed
@polywrap/core-js
:
- PR-32 Rename
getEnvFromUriHistory
togetEnvFromResolutionPath
Bugs
@polywrap/client-js
- PR-32 Improved Browser Compatability
- Building the JS client into browser-based applications no longer requires custom polyfills to remove Node.JS dependencies.
@polywrap/client-cofig-builder-js
- PR-37 Add
@polywrap/plugin-js
as a Dependency- This resolves some package resolution warnings that are emitted from npm when installing the client-config-builder.
@polywrap/wasm-js
:
- PR-30 Properly Serialize Empty Wrap Environment
- 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.