Skip to content

Conversation

@jquense
Copy link
Member

@jquense jquense commented Jan 8, 2025

Bumps the build and replaces a bunch of tooling and config with inlined stuff so that it's easier to update later. I went with as simple a config as i could.

Also updates the build to rely solely on exports instead of the cherry picked directories, I think that's ok node have supported this for years and bundlers about as long.

still gotta test a bit and some day i'll have to figure out how to update these doc sites build on projects i've abandoned 😬

@jquense jquense requested a review from kyletsang January 8, 2025 20:31
Copy link
Collaborator

@kyletsang kyletsang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Should we drop React 16+17 and make this the next major?

@jquense
Copy link
Member Author

jquense commented Jan 9, 2025

I am happy to do that, are we ok bumping RB as well? It does seem safer that way

@kyletsang
Copy link
Collaborator

Yep that works. I was thinking of starting the next major version of RB too. I do want to clean up/simplify some stuff

@jquense jquense merged commit 66a41bb into main Jan 10, 2025
6 checks passed
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.

3 participants