@web3api/manifest-schemas - npm Package Versions

Web3API 0.0.1-prealpha.45

Features

• @web3api/tracing-js: Support service name configuration.

Web3API 0.0.1-prealpha.44

Features

• @web3api/client-js: Use Fleek's IPFS gateway.

Web3API 0.0.1-prealpha.43

Features

• @web3api/client-js: Added the client.subscribe(...) method, enabling users to easily send queries at a specified frequency.

Bugs

• @web3api/tracing-js: Replaced the util-inspect dependency with a browser compatible one.

Web3API 0.0.1-prealpha.42

Bugs

• @web3api/schema-parse: Removed unnecessary sanitization for imported methods without any arguments.

Web3API 0.0.1-prealpha.41

Features

• @web3api/schema-parse: Added support for JSON as a base type.
• @web3api/ens-api: Merged in an initial version of the ENS Wasm based Web3Api.
• web3api.build.yaml: Added support for the linked_packages property, allowing you to link local packages into the dockerized build-env.

Bugs

• @web3api/schema-compose: Fixed an invalid GraphQL bug that occured when an imported query method did not have any arguments.

Web3API 0.0.1-prealpha.40

Features

• @web3api/client-js: Added getManifest(...), getFile(...), and getSchema(...) methods to the client, simply provide a URI.
• @web3api/cli: APIs can now define metadata via the web3api.meta.yaml manifest file. Upon compiling your project, the CLI will copy all referenced metadata files into the build directory. Applications such as The Polywrap Hub will use this metadata file to display details about your package such as: title, description, icon, example queries, etc.

Bugs

• @web3api/schema-parse: Duplicate fields on object & query types are not detected, and will cause a compiler error.

Breaking Changes

• @web3api/client-js: Removed the loadWeb3Api(...) method from the client. This is because we do not want to give the user of the client a direct reference to the underlying API class object. Since garbage collection will delete these, having the user able to hang onto references, will result in them staying in memory.

Web3API 0.0.1-prealpha.39

Features

• @web3api/client-js: Added https://polywrap-dev.mypinata.cloud and https://ipfs.infura.io as default fallback IPFS providers.

Bugs

• @web3api/ipfs-plugin-js: Fallback providers are now used if an error is encountered, not just for timeouts.

Web3API 0.0.1-prealpha.38

Breaking Changes

• @web3api/client-js: Removed the usage of _w3_init, as it's unnecessary and caused issues with adding Rust-Wasm support.

Web3API 0.0.1-prealpha.37

Bugs

• @web3api/asyncify-js: Fixed problem when Wasm modules are larger than 4 KB. More info here.
• @web3api/client-js: Use new asyncify-js package, where instantiation is asynchronous.

Web3API 0.0.1-prealpha.36

Features

• Upgrade all JavaScript plugins to use the new w3 plugin codegen command. The command generates typings based on the GraphQL schema of the plugin. This ensures the plugin's resolvers match 1:1 with the GraphQL schema.