-
Notifications
You must be signed in to change notification settings - Fork 15
chore(ci): unblock stalling documentation build #394
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
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.
we should move to docusaurus 3.7 with rspack, it should solve this too
Good catch! The |
|
||
.tagline span { | ||
color: var(--ifm-color-primary); | ||
} |
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.
The new rspack
bundler (or adjacent tooling) seems to wrongly resolve !important
CSS rules (the tagline had blue words instead of transparent). Removing this rule seems to fix the issue (and not break anything else.)
Its already set up on the main docs repo, we need to keep the swc loader disabled since that doesn't work well (or should I say at all) with styled components. https://github.com/apify/apify-docs/blob/master/docusaurus.config.js#L22 Although it might be fine in this repo, the place where we use it is in the landing pages like http://docs.apify.com/api |
Huh, it seems that |
Closing as solved by apify/apify-docs#1452 |
I would still merge this one with the docusaurus update, or is there any reason not to? |
Oh yeah, that makes sense. Let me regenerate the lockfile anew (there seem to be quite a lot of unrelated changes as a result of the debugging) and we can switch to |
Bumps the available heap size for the doc-building Docusaurus process. We already do this e.g. in Crawlee JS.