-
Notifications
You must be signed in to change notification settings - Fork 26.2k
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
ci(workflow): deploy rustdocs for turbopack #61958
Conversation
5274114
to
22e8e97
Compare
Tests Passed |
Stats from current PRDefault BuildGeneral
Client Bundles (main, webpack)
Legacy Client Bundles (polyfills)
Client Pages
Client Build Manifests
Rendered Page Sizes
Edge SSR bundle Size
Middleware size
Next Runtimes
|
61eec16
to
f0972ee
Compare
### Description To replaced by vercel/next.js#61958 Closes PACK-2470
Currently it's work in progress, the only package available is [Turbo tasks-fs](turbo_tasks_fs/index.html) | ||
|
||
[comment]: # 'Temporary index page document' |
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.
?
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.
It's a markdown comment. Will go away when updating docs.
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.
Why add it though
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.
To explicitly state index is work in progress temporary, just to render content. Could be a visible to the rendered page, in any case would like to note for anyone see this.
fi | ||
fi | ||
|
||
RUSTDOCFLAGS="-Z unstable-options --index-page $(pwd)/packages/next-swc/docs/index.md" cargo doc -p turbo-tasks-fs --no-deps |
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.
Why turbo-tasks-fs
?
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.
only pkg I can casually find to build with rustdoc without 1. huge time to check CI 2. does not actually raises build error.
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.
I don't see the point in adding this just for turbo-tasks-fs
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.
yes, there's no point for doc itself. It's setup that ensures
- we can build cargo docs without build error
- we can deploy it correctly.
It's just starting point to actually add docs.
- name: Install Rust | ||
uses: ./.github/actions/setup-rust | ||
- name: Deploy preview docs | ||
if: ${{ needs.build.outputs.isRelease != 'true' }} |
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.
this could just be a ternary on DEPLOY_ENVIRONMENT
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.
Could be, but same as the script itself this mimics pattern setup in other deploy work - making it consistent so later easy to find & replace as needed.
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.
just because the existing code is bad doesn't mean the new code has to be as well
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.
is it bad though? I honestly don't think it's that bad, especially isRelease
is universal flag for all of the existing next.js CI's workflow to work with release. It might be different way, but I don't see reason to try other pattern over established pattern.
f0972ee
to
5c2df9f
Compare
What
We'd like to deploy generated rustdocs from turbopack & related packages (next-swc), setting up a CI workflow to automate those.
Since we need next.js side packages to build docs, this CI sets up things in this repo.
Closes PACK-2375.