vitest-pool-assemblyscript 0.8.0 → 0.9.1

package/BINARYEN_VERSION

@@ -1 +1 @@
-version_124
+version_129

package/README.md

@@ -65,16 +65,16 @@
 
 ## Status
 
-This project is relatively new to the scene, but is stable and is being improved every day. Please give it a try!
+While relatively young, this project is stable and is being improved every day.
 
-All [listed features](#features) are working and assumed to be bug-free ([please report any](https://github.com/themattspiral/vitest-pool-assemblyscript/issues/new)).
+All [listed features](#features) are working, tested, and assumed to be bug-free.
 
 | Item | Status |
 |---|---|
 | [`describe()` and `test()` APIs](#writing-tests) | - stable<br/>- no breaking changes expected |
 | [`expect()` API](docs/matchers-api.md) | - stable<br/>- no breaking changes expected<br/>- more matchers coming soon |
 | Code Coverage / Instrumentation | - function coverage stable [across platforms](#compatibility)<br/>- branch & line coverage coming soon |
-| Hybrid Coverage Provider | - stable<br/>- v8 JS delegation, side-by-side JS coverage<br/>- istanbul JS delegation coming soon
+| Hybrid Coverage Provider | - stable<br/>- v8 JS delegation, side-by-side JS coverage<br/>- JS delegation to istanbul provider coming soon
 
 See Also:
 - [Current Limitations & Roadmap](#current-limitations--roadmap)
@@ -160,21 +160,20 @@ npx vitest run
 - Use familiar `vitest` commands, CLI spec and test filtering, watch mode
 - Works with Vitest UI, reporters, and coverage tools
 - Project (workspace) config allows coexisting AssemblyScript pools and JavaScript pools
-- Hybrid Coverage Provider unifies test reports from multiple pools (delegating to v8 for JS/TS coverage)
-- Coverage reporting using any vitest reporter (`html`, `lcov`, `json`, etc)
-- Dual vitest 3.x / 4.x support
+- Hybrid Coverage Provider unifies test reports (`html`, `lcov`, `json`, etc) from multiple pools (delegates to v8 provider for JS coverage)
+- Supports vitest 3.x and 4.x
 
 ### Per-Test WASM Isolation
-- Each AssemblyScript test file is compiled to a WASM binary once
-- Each test case runs in a fresh WASM instance (reusing the compiled binary)
+- Each AssemblyScript test **file** is compiled to a WASM binary
+- Each AssemblyScript test **case** runs in a fresh WASM instance (reusing the compiled binary)
 - One crashing test doesn't kill the rest within the same suite
-- `toThrowError()` matcher can be used to catch and expect specific errors (which trap and abort)
+- `toThrowError()` matcher can catch and expect specific errors (which trap and abort)
 
 ### Familiar Developer Experience
 - Suite and test definition using `describe()` and `test()` in AssemblyScript
 - Inline test option configuration for common vitest options: `timeout`, `retry`, `skip`, `only`, `fails`
 - Assertion matching API based on vitest/jest `expect()` API
-  - `.not`, `toBe`, `toBeCloseTo`, `toEqual` (with caveats*), `toStrictEqual`, `toBeGreaterThan`, `toBeGreaterThanOrEqual`, `toBeLessThan`, `toBeLessThanOrEqual`, `toHaveLength`, `toThrowError`, `toBeTruthy`, `toBeFalsy`, `toBeNull`, `toBeNullable`, `toBeNaN`
+  - `.not`, `toBe`, `toBeCloseTo`, `toEqual`, `toStrictEqual`, `toBeGreaterThan`, `toBeGreaterThanOrEqual`, `toBeLessThan`, `toBeLessThanOrEqual`, `toHaveLength`, `toThrowError`, `toBeTruthy`, `toBeFalsy`, `toBeNull`, `toBeNullable`, `toBeNaN`
   - See [Matchers API](docs/matchers-api.md) for details and differences from JavaScript
 - Highlighted diffs for assertion and runtime failures, which point to source code
 - Source-mapped WASM error stack traces (accurate AssemblyScript source `function file:line:column`)
@@ -265,7 +264,7 @@ The overall goal is tight vitest experience integration - most CLI commands, rep
 
 **Q: Is this an official vitest project?**
 <br/>
-**A:** No, this is a third-party community project. It's not affiliated with or endorsed by the vitest team, though we're grateful for their extensible architecture that makes projects like this possible, and the [other open-source projects](#prior-work) that provide vital functionality and reference architecture.
+**A:** No, this is a third-party, community project. It's not affiliated with the Vitest team or VoidZero directly, though we're grateful for their open-source code and intentionally extensible architecture which make projects like this possible, and to the [other open-source projects](#prior-work) that provide vital functionality and reference architecture.
 
 **Q: Are you a company? A bot?**
 <br/>
@@ -406,7 +405,6 @@ These are known limitations which are currently being worked on.
 - **Function-level coverage only**: No statement, branch, or line coverage yet
 - **No lifecycle hooks**: No setup/teardown hooks yet
 - **Watch mode handles specs only**: Re-runs test files when they are directly changed, but not yet based on changed source files
-- **`toEqual` doesn't reflect**: Doesn't yet support deep inspection of user-defined objects
 
 ### Near Future Roadmap
 
@@ -418,7 +416,6 @@ These are known limitations which are currently being worked on.
 **Epic: Testing DX**
 - Lifecycle hooks (`beforeEach`, `afterEach`, `beforeAll`, `afterAll`)
 - Watch mode: re-run applicable tests on source file changes
-- `toEqual` reflection for deep equality inspection of user objects
 - `describe.for/each` and `test.for/each`
 - expect.soft to prevent fail-fast behavior
 - Allow delegating JS/TS to istanbul coverage provider in addition to v8