-
Notifications
You must be signed in to change notification settings - Fork 104
chore: bump Docusaurus + React, use yarn
#1615
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
bdf2e52
to
deffb20
Compare
Preview for this PR was built for commit |
Preview for this PR was built for commit |
ca8e9e5
to
a12fa45
Compare
Preview for this PR was built for commit |
Preview for this PR was built for commit |
While the update seems to work with
Weirdly enough, this doesn't seem to be the problem with |
45b5c32
to
50665c2
Compare
yarn
Btw if we're moving this repository to yarn, the docs-private flow also needs to be moved to it, otherwise you'll get WILD issues that make no sense |
@vladfrangu could you take a look locally too to see if we can stay on NPM? I'll try to do the same later today or tomorrow, feels weird that the module resolution wouldn't work like this. Maybe we just need to use |
Bumps Docusaurus to 3.8.0 and React to version 19. Switches the package manager to
yarn
because of faulty version resolution withnpm
.