@dorgjelli-test/manifest-schema - npm Package Versions

Web3API 0.0.1-prealpha.49

Features

• @web3api/fs-plugin-js: Added a "File System" plugin, which implements the uri-resolver interface, enabling users to load Web3API packages from their local filesystem. For example, a user could specify the URI /fs/path/to/package/directory.
• Upgraded the toolchain's Node.JS version to 16.13.0, which solves compatibility issues with Mac computers using the new M1 processor.

Bugs

• @web3api/cli: Fixed the w3 query ... command's recipe variable parsing logic, better supporting arrays and objects.
• @web3api/schema-compose: Improved import parsing, and added support for recursive schema imports.

Web3API 0.0.1-prealpha.48

Bugs

• @web3api/test-env-js: Allow the usage of this package as an npm package outside of the monorepo folder structure.

Web3API 0.0.1-prealpha.47

Features

• @web3api/client-js: Add the Graph Node plugin to the client's default configuration.
• @web3api/ethereum-plugin-js: Add the encodeFunction query method, allowing callers to encode smart contract methods w/ argument values.

Web3API 0.0.1-prealpha.46

Bugs

• @web3api/core-js: Properly check for "undefined" values in query arguments.
• @web3api/wasm-as: Improved MsgPack deserialization of integers (signed & unsigned).

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