Version 0.7

[brainkim]

• Allow refresh() to be passed a callback.
• Remove deprecated special props
• Switch to a two-pass render Switch to a two-pass render #284 async rendering of children: should be properly coordinated #68
  • Fix hydration
  • Move unmount logic to the commit phase
• Revamp error handling Revamp Async Generator Error handling #287
  • Stop unhandled promise rejections
  • Make sure the promise passed back into async gen for await of components reject.
• Create and retain Text nodes via the text() method rather than via the arrange() method. Text Node improvements #288
  • Refactor RenderAdapter methods
  • Allow Text with ref
  • Tests for Text element
• Switch default async generator behavior to the same as for...of Change default async generator component behavior to pause at yields #291?
• Async unmounting Async unmounting #245
  • preserve index
• Stabilize internal Renderer API
  • RenderAdapter remove() method
    • Call during unmount
    • pass info about whether the host node removal is “nested”
  • Make patch() take the full props and oldProps.
  • Pass host info as objects
  • Think really carefully about all the methods and their names.
• Allow the copy prop to mark specific props for copying Allow the copy prop to mark specific props for copying #292
  • selective copying for props
  • selective copying for children
• Improved hydration Implement robust hydration warning system #289
  • Warn on hydration props mismatch
  • boolean hydrate prop
  • selective hydrate for props
  • selective hydrate for children
• Allow class to take objects (classnames, clsx) Allow class prop to take objects #294
• Async mounting/updating? Deferred mounting with async schedule() callbacks #290
  • Allow schedule to return a promise to defer mounting
  • Allow schedule to return a promise to defer updating
• Implement Suspense/SuspenseList/memo() and add them to an async.ts utility module
• isExecuting/isUnmounted
• handle attributes with namespaces not necessary in modern browsers
• Rename this.flush() to this.after()
• Don’t remove DOM nodes we don’t control. Stop blowing away the children of DOM nodes which we render into #158

[brainkim]

I’m stuck working on some tricky promise rejections.

From Copilot:

Analysis in Light of the Bug

The Bug: Async generator yields, then throws, but no unhandled rejection

Your reported bug suggests that after yielding, when an async generator throws, the error is not resulting in an unhandled promise rejection as expected.

How These Changes Address (or Don't Address) the Bug

The tests now explicitly check for unhandled rejections and will fail if the rejection does not occur.
However, there are no changes in the actual rendering/runtime code (e.g., in src/dom.ts or src/crank.ts) that change how thrown errors from async generators are surfaced. The bulk of the logic changes are in the test suite, not the core async generator or error propagation logic.
If the bug persists, it likely means the runtime (renderer) is catching errors internally and not letting them propagate as unhandled rejections. The new or unskipped tests will now fail, demonstrating the bug more clearly, but unless the renderer’s error handling code is changed, the underlying behavior will not change.

Recommendations

If your goal is to fix the bug, you will need to review the control flow in the renderer (likely in src/crank.ts or the main rendering loop in src/dom.ts), and ensure that errors thrown from async generators which are not caught by user code are not swallowed or turned into handled rejections.
The current PR is a great step for surfacing the bug and making the test suite fail where it should, but it does not, on its own, fix the underlying issue.
Summary

The changes in test/errors.tsx robustly surface and assert on error propagation and unhandled promise rejections from async generators.
The changes in src/dom.ts are mostly unrelated to error propagation, focusing on props/children handling.
The core bug (unhandled promise rejection not occurring) is not fixed by these changes—they only make the bug visible in tests.
To actually fix the bug, changes are needed in the renderer’s async generator error handling logic.