Skip to content

v3#174

Draft
rschristian wants to merge 5 commits intomainfrom
v3
Draft

v3#174
rschristian wants to merge 5 commits intomainfrom
v3

Conversation

@rschristian
Copy link
Member

@rschristian rschristian commented Nov 8, 2025

WIP, just collecting some changes we'd probably want to make. Lmk if anyone disagrees with any of this. I've done a fair bit of rebasing & after the fact tweaking so probably wouldn't recommend looking at the diff of linked PRs (descriptions & comments fine tho), they might be out-of-date with the squashed commits here.

TODO yet:

@rschristian rschristian force-pushed the v3 branch 2 times, most recently from 0bc3c0f to 5bb1614 Compare November 8, 2025 06:23
@rschristian rschristian force-pushed the v3 branch 2 times, most recently from 3a12007 to c8e911f Compare November 9, 2025 05:43
* chore: Bump deps

* chore: Switch to newer TS module resolution

* fix: skipLibCheck to get around Rollup's broken plugin types

* test: Correct test utils
* refactor: Switch to JS

* ci: No more build script

* ci: Add type-checking step

* chore: Patch broken types in '@rollup/pluginutils'
@Sidnioulz
Copy link

Sidnioulz commented Feb 24, 2026

@rschristian it could be useful to have a prerelease canary for this branch with e.g. a beta NPM dist-tag. It would allow downstream projects to anticipate compatibility issues by testing their CI against your next release.

@rschristian
Copy link
Member Author

This branch is just my noodling, I have 0 buy in from any other maintainers yet. No need for a prerelease.

@Sidnioulz
Copy link

@rschristian fair enough. I'm setting up a preact prerelease CI sandbox at Storybook and would've liked the opportunity to also test this package as we heavily depend on it, but only you can tell whether or not it's worthy of a RC status :)

@rschristian
Copy link
Member Author

Don't worry, we'll create a proper beta release when appropriate. Like I said, this is purely my noodling & my wishlist, along with some topics we've vaguely talked about -- this branch could just get nuked yet.

@rschristian rschristian force-pushed the v3 branch 2 times, most recently from 7ce61bd to 202e295 Compare March 10, 2026 21:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants