-
Notifications
You must be signed in to change notification settings - Fork 411
chore: update docusaurus and dependencies #2193
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR updates the Docusaurus packages along with several other dependencies to newer versions.
- Updated Docusaurus dependencies from 3.7.0 to ^3.8.0 with caret versions now allowing minor updates.
- Bumped versions for axios, prismjs, redocusaurus, and various devDependencies.
- Introduced tailwindcss in dependencies while removing it from devDependencies.
Comments suppressed due to low confidence (2)
package.json:33
- The change from a fixed version to a caret version allows for automatic minor updates; please confirm that this aligns with the project's stability requirements.
"@docusaurus/core": "^3.8.0",
package.json:71
- Tailwindcss has been moved from devDependencies to dependencies; please verify that this change is intentional and that the package is used in production code.
"tailwindcss": "4.1.8"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
issues with CSS and fonts
i can take a closer look next week
Damn :( |
7385a35
to
effc0fa
Compare
Can't repro locally, maybe a build issue |
yea locally it builds and looks fine to me too. might be something related to the preview deploy... just merge it and roll back if there is an issue? no other idea atm. |
I triggerd another build without cache, let's see |
After hard-reset, the styling is still broken, so I think it's some type of issue in the upgrade. I think @jonas-jonas wants to take a look when he's done with other work |
55ab03c
to
bff407b
Compare
bff407b
to
c0fa2d7
Compare
c0fa2d7
to
b50d097
Compare
b50d097
to
effc0fa
Compare
now that #2197 is merged, can this be closed or is there something specific in here? |
No description provided.