mnfst-render
v0.5.66
Published
Render Manifest sites to static HTML for SEO
Maintainers
Readme
mnfst-render
Static renderer for Manifest projects.
Usage
npx mnfst-render --root .The command reads manifest.json and writes rendered pages to manifest.render.output (default website).
Dependencies
Rendering needs Puppeteer. Projects that use data-tailwind also need Tailwind to compile a static stylesheet. Install them once for every project on the device:
npm i -g puppeteer tailwindcss @tailwindcss/cliOr per project:
npm i -D puppeteer tailwindcss @tailwindcss/cliA project install takes precedence. Otherwise mnfst-render uses the global install (npm root -g, plus any NODE_PATH entries). Serverless builds can use puppeteer-core with @sparticuz/chromium instead of puppeteer.
Concurrent renders
Only one render may write an output directory at a time. While running, a render holds <output>.mnfst-lock (next to the output directory) recording its PID, host, start time, and command. A second render against the same output exits immediately with an error naming the running render.
A lock left behind by a process that no longer exists is taken over automatically. To take over a lock regardless, pass --force-lock; the render that lost the lock will not replace the output when it finishes.
