@polywrap/config-bundle-types-js - npm Package Versions

Polywrap Origin (0.12.1)

Bugs

@polywrap/wrap-manifest-types-js:

• PR-68 Browser compilation fix
  • The "semver" sub-dependency (version 7.5.0) has a problem building for the browser, upgrading to 7.5.4 fixes this.
    • source: https://github.com/npm/node-semver/issues/554

Polywrap Origin (0.12.0)

Features

@polywrap/sys-config-bundle-js:

• PR-56 Wrapscan URI Resolution Using Sys Bundle
  • Resolving wrapscan.io/ URIs is now possible by simply adding the "sys" bundle to your client's configuration.
  • The "sys" bundle now includes: wrapscanResolver, ipfsResolver, and ipfsHttpClient.
• PR-55 GitHub URI Resolution Using Sys Bundle
  • Resolving github.com/ URIs is now possible by simply adding the "sys" bundle to your client's configuration.
  • NOTE: this requires a URI.txt file located in the directory you're linking to on GitHub.

Breaking Changes

@polywrap/client-js:

• PR-62 Migrate All URIs To Wrapscan (Remove ENS URIs)
  • All URIs used within the client's packages (uri-resolver-extensions, config-bundles, etc) have been migrated to wrapscan.io/ based URIs.
  • All ens/ URIs have been deprecated, but resolving ens/ URIs is still supported.

Bugs

@polywrap/core-js:

• PR-61 URI Should Start W/ Word Character
  • URIs should not start with non-word characters, for example ../.

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 into wrap://https/domain.com/path
    • ipfs://QmHASH into wrap://ipfs/QmHASH

@polywrap/client-config-builder-js:

• PR-45 Modular Config Bundles
  • The DefaultBundle has been broken apart into two separate bundles: sys and web3.
  • addBundle(...) has been added to the ClientConfigBuilder interface.
  • addDefaults() now calls addBundle("sys") and addBundle("web3") internally.

@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.

@polywrap/web3-config-bundle-js:

• PR-45 Bundled Web3 Plugins & Resolvers
  • The web3 bundle includes: ethereumProviderV1, ethereumProviderV2, ipfsHttpClient, ipfsResolver, ensTextRecordResolver, ensResolver, ensIpfsContenthashResolver.

@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 type Bundle.

Breaking Changes

@polywrap/client-config-builder-js:

• PR-47 Renaming For Improved Accuracy
  • Renamed ClientConfigBuilder to PolywrapClientConfigBuilder
  • Renamed IClientConfigBuilder to ClientConfigBuilder
  • Renamed addWrapper(s) to setWrapper(s)
  • Renamed addPackage(s) to setPackage(s)
  • Renamed addRedirect(s) to setRedirect(s)

@polywrap/core-js:

• PR-32 Rename getEnvFromUriHistory to getEnvFromResolutionPath

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.