rsnext/scripts/deploy-turbopack-docs.sh

#!/usr/bin/env bash
set -euo pipefail

PACKAGES="-p next-swc-napi -p next-api -p next-build -p next-core -p next-custom-transforms"
RUSTDOCFLAGS="-Z unstable-options --enable-index-page" cargo doc $PACKAGES --no-deps
ci(workflow): deploy rustdocs for turbopack (#61958) ### 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. 2024-02-13 00:14:36 +01:00			`#!/usr/bin/env bash`
			`set -euo pipefail`

docs(turbopack): build more docs (#61977) ### What This PR changes setup for the turbopack documentation. Long story in short, we want to 2 types of documentation: one for high level description (archtecture, etcs) and another for the api doc. rustdoc / cargo doc unfortunately doesn't support to integrate both easily. PR adds mdbook setup to workaround those - instead of using rustdoc's index as entrypoint, mdbook becomes an entrypoint to rustdoc. This allows to host plain text document, and also able to access full rustdoc pages. preview: https://turbopack-rust-docs-b6qta4xdq.vercel.sh/ rustdoc: https://turbopack-rust-docs-b6qta4xdq.vercel.sh/rustdoc/index.html Closes PACK-2475 Closes PACK-2468 2024-02-13 21:17:25 +01:00			`PACKAGES="-p next-swc-napi -p next-api -p next-build -p next-core -p next-custom-transforms"`
docs(turbopack): move docs to separate (#62069) ### What For better organization, extracting docs into separate location. Closes PACK-2494 2024-02-15 17:05:48 +01:00			`RUSTDOCFLAGS="-Z unstable-options --enable-index-page" cargo doc $PACKAGES --no-deps`