@polywrap/http-plugin-js - npm Package Versions

Polywrap 0.0.1-prealpha.93

Breaking Changes

• PR-986 WRAP build artifacts have been refined:
  • Wasm module name changed from module.wasm to wrap.wasm
  • Polywrap manifests are no longer written to build folder (except for project metadata).
  • The wrap.info is now the primary manifest file describing the wrapper:
    • { version, type, name, abi }
    • source
    • encoded as msgpack binary file
  • schema.graphql remains but will be deprecated for wrap.info's built-in abi.

Polywrap 0.0.1-prealpha.92

Features

• PR-1006 polywrap-wasm-rs: Add Rust encoder unit tests.
• PR-967 polywrap CLI, polywrap-wasm-rs, @polywrap/wasm-as, @polywrap/schema-parse, @polywrap/schema-compose, @polywrap/schema-bind, @polywrap/core-js, @polywrap/client-js: Environment configuration for wrappers was refactored to enable environments at the method level, remove client env sanitization and adding support for Rust. @env annotation was introduced for methods declared in wrappers's schemas.
• PR-1005 @polywrap/core-js, @polywrap/client-js: Refactored client.subscribe to use invoke syntax.

Breaking Changes

• PR-967 Wasm runtime (polywrap-wasm-rs, @polywrap/wasm-as) changed invoke signature and imports/exports, schema pipeline (@polywrap/schema-parse, @polywrap/schema-compose, @polywrap/schema-bind) now supports external env imports and TypeInfo and @env annotation for methods, polywrap changed compiler's imports, @polywrap/core-js changed Plugin interface, @polywrap/client-js changed environment model implementation.
• PR-1005 @polywrap/core-js, @polywrap/client-js: Refactored client.subscribe to use invoke syntax.

Polywrap 0.0.1-prealpha.91

Features

• PR-989 @polywrap/core-js: Add job status in workflow job's result object.
• PR-992 polywrap CLI: Allow configuring the client using the --client-config on all applicable commands.
• PR-1000 @polywrap/core-js: Added the encodeResult property to InvokeOptions.
• PR-1000 @polywrap/core-js: Introduced the concept of Invoker and Invocable.
• PR-988 polywrap CLI, wasm/rust: Updates to the default build-image (Dockerfile):
  • Added the system dependencies clang, llvm and build-essentials.
  • Added steps to remove any wasm-bindgen imports that may have been injected.

Bugs

• PR-1000 Fixed inconsistencies around ArrayBuffer and Uint8Array.
• PR-1000 @polywrap/client-js: The noDecode flag (renamed to encodeResult) now enfoces the decoding properly, where before it could get confused with returning Bytes from a wrapper.
• PR-981 polywrap-wasm-rs: Remove the wrap-invoke feature because it is not being used at the moment.

Breaking Changes

• PR-980 @polywrap/schema-parse: Rename TypeInfo from Abi.

Polywrap 0.0.1-prealpha.90

Features

• PR-912 PR-930 PR-958 All URI resolver extensions have been decoupled and moved into their own plugin packages:
  • @polywrap/fs-resolver-plugin-js
  • @polywrap/ipfs-resolver-plugin-js
  • @polywrap/ens-resolver-plugin-js
• PR-912 @polywrap/file-system-interface has been created to help standardize FileSystem wrapper implementations.
• PR-930 @polywrap/ipfs-interface has been created to help standardize IPFS wrapper implementations.

Bugs

• PR-957 @polywrap/schema-bind: plugin/typescript module config type interfaces no longer inherit from Record<string, unknown>, making them more type-safe and less generic.

Breaking Changes

• PR-937 PR-960 The term Nullable has been changed to Optional within the wasm wrapper codegen. Additionally in wasm/assemblyscript the Nullable<T> type has been changed to a rust-style Optional<T> type.
• PR-972 The term input in the context of invocations has been renamed to args.
• PR-976 The invocation resultFilter option has been deprecated, as it is a needless & unused feature.

Polywrap 0.0.1-prealpha.89

Features

• PR-903 polywrap CLI: Recipes have been re-worked into composable workflows, and they can be run using CLI commands.
• PR-951 polywrap CLI: Docker Buildx output option has been removed.
• PR-944 @polywrap/schema-bind, @polywrap/wasm-as: Nullable type has been replaced with Option in the Assemblyscript schema bindings.
• PR-938 @polywrap/schema-bind, @polywrap/wasm-as: Rollback of JSON serialization in the Assemblyscript schema bindings.

Bugs

• PR-946 @polywrap/test-env-js: Path fix for npmCLI test utility.

Breaking Changes

• PR-903 polywrap CLI: Running recipes via the polywrap query ... command has been deprecated in favor of a new workflows system, accessible via the polywrap run ... command.
• PR-944 wasm/assemblyscript Wrappers: Nullable type has been removed in favor of Option which also has a different interface.
• PR-938 wasm/assemblyscript Wrappers: JSON serializer and deserializer, and related methods fromJson and toJson have been removed in favor of parse and stringify.

Polywrap 0.0.1-prealpha.88

Bugs

• Various CI/CD fixes.

Polywrap 0.0.1-prealpha.87

Features

• PR-928 @polywrap/manifest-schemas: Inline documentation has been added to manifest JSON-schemas.
• PR-933 Validation package @polywrap/package-validation has been implemented to validate WASM wrapper packages.

Bugs

• PR-932 @polywrap/schema-bind: Minor fix for JSON type schema bindings
• PR-935 @polywrap/test-env-js: Path fix for npmCLI test utility

Polywrap 0.0.1-prealpha.86

Features

• PR-923 The Polywrap brand has been applied to the codebase.
• PR-906 The concept of Mutation and Query modules has been deprecated. Now all wrapper methods are defined within a single Module.

Breaking Changes

• PR-923 All prior integrations using the "Web3API" packages must upgrade to the new "Polywrap" equivalents.
• PR-906 All wrappers created prior to this change are incompatible.