@hirosystems/clarinet-sdk-wasm - npm Package Versions

1.0.6 (2022-11-10)

New Features

• Ability for chainhook-node to start with custom config (473c86ba)
• Draft bitcoin replay implementation (8580092e)

Bug Fixes

• Filter out boot contracts from requirement dependencies (34fbcf96)
• Deno expect events (8bdcd392)
• Fix issue with check-checker requiring checking on bools (ef738fe3)

Refactors

• Add serverless dependency in cbtc example and upgrade dependencies (f065f2b)
• Get_bitcoin_proof (5a3a8ee9)

1.0.5 (2022-11-03)

New Features

• Many chainhooks enhancements: event payload augmented, new predicates (segwit, etc) implemented. Documentation coming soon!
• Introducing clarity-jupyter-kernel (1c118513)
• Ability to use low/medium/high cost dynamic presets in deployment plans (86219c4e)
• Ability to send STX in deployment plans (c9e3bac4)

Bug Fixes

• Termination in clarinet integrate --no-dashboard mode fixed (2cdb09a6)
• Check print predicate for contained value (0f5956dc)
• Improved keyword recognition in VSCode grammar file (e690b371, 119dce57)
• Fixed stacks-js-helper generator (11562ae7)

Chores

• Types improvements clarinet deno library (3bc5c51c)
• Add tests to the clarinet deno library (d5b7555d, 062a7144)

1.0.4 (2022-10-17)

New Features

• Devnet chainstate now lives in cache directory specified in Clarinet.toml (a6fb383f)
• Ability to pass wildcards for chainhook testing (08f75a2a)
• Ability to use write-to-file as action (chainhooks) (fb19e392)
• Introduce stacks-network component (ace64116)

Bug Fixes

• Bump ingestion limits to 5 mb (e4d539da)
• Fix invalid bitcoin txid (03783a41)
• Fix coverage tracking (1a4836d1)
• Fix crash occuring on NFTMintEvent (d5dc3fc0)
• Resolve boot contract in LSP (ad34037c)
• Better error (d42f7ed6)
• Performance optimisation with parser v2 (c1712489)

1.0.0 (2022-10-06)

New Features

• Introducing our brand new re-architected VSCode extension (README)
• All of our tools (REPL, LSP, Clarinet) are now directly derived from the canonical Clarity VM (#512, #535, #544)
• Ability to trigger chainhooks from unit tests (#564)
• Deno integration upgraded and revisited (#511)
• Ability to specify Deno import maps (#511)
• Ability to specify TS config files (#555)
• Ability to cache Deno libraries locally (a2c2ded3)
• Bitcoin deployment plans now supports transfers to P2WPKH addresses (c50a4c27)
• Ability to detect outdated deployment plans and display diffs (#365)

Bug Fixes

A myriad of issues were addressed in this new version, the most notable being:

• Cannot make http request from within clarinet test (#566)
• Clarinet CPU usage spiking to 100% when using clarinet integrate (#545)
• Clarinet console crashes when it errors (#541)
• Unhandled Division By Zero exception (#525)
• Handle errors from callReadOnlyFn in tests (#407)
• Arithmetic underflow crashes clarity-repl instead of displaying error (#471)
• Improve debugability of chain.mine_block() (#91)

Documentation

• Added new example - How to use Chainhooks for indexing data (cdeca648)
• Added OpenAPI spec for Chainhooks (01e8979c)

Compatibility Issue

Clarinet v1.0.0 is not currently backwards-compatible with older versions of the Clarinet deno library. If you are upgrading Clarinet to Clarinet v1.0.0, you will need to enter the following import command in your test files to perform this update.

import { … } from 'https://deno.land/x/clarinet@v1.0.2/index.ts';

Note The v1.0.0 library is not compatible with Clarinet versions <= 0.33.0. Prior versions of the library also will not be compatible with versions >= 1.0.0 of Clarinet because the layer in charge of the communication between Typescript and Rust was upgraded. If you are using Clarinet in a Github Action, and using the tag latest (now pointing to v1.0.0), the tests will fail if the import upgrade task is not performed. If you do not want to upgrade, this is possible; however, you will need to specify the docker tag v0.33.0, instead of latest.