MetaBake (mbake) CLI is an open-source, extensible low-code productivity bundler and builder designed for creating static websites and web applications, leveraging Pug and JAMstack principles. As of version 8.5.4, it provides out-of-the-box features like Pug compilation, livereload, Sass/SCSS compilation with autoprefixing, and TypeScript compilation. Its core differentiator is simplifying web development by abstracting away complex build configurations, allowing developers to write cleaner code quicker for various projects including static sites, custom elements, CMS, e-commerce, and CRUD applications. It facilitates a gradual adoption approach, enabling rapid development with a focus on simplicity and efficiency. While it doesn't specify a strict release cadence, it indicates active development. The tool focuses on generating static content that can be served efficiently via CDNs, using standard web technologies like HTML, CSS, and JavaScript, making it accessible to a broad audience.
npm install mbakeVerified import paths — ran on the pinned version, not inferred.
This quickstart demonstrates how to install mbake globally and start a basic website with livereload using Pug and a data YAML file.
Upgrade your Node.js installation to version 14.0.0 or newer using a version manager like `nvm` or by downloading the latest LTS from nodejs.org.
Ensure `index.pug` and `dat.yaml` are correctly placed in the directory you are compiling. Refer to the documentation for specific file structure requirements for different features (e.g., Sass, TypeScript).
Always install `mbake` globally using `npm i -g mbake` to ensure the `mbake` command is available in your system's PATH.
Run `npm i -g mbake` to install the package globally. If already installed, verify your system's PATH environment variable.
Update your Node.js to version 14.0.0 or newer. For example, using nvm: `nvm install 16 && nvm use 16`.
Ensure you are running `mbake` from the root directory of your project, where `index.pug` and `dat.yaml` are located, or specify the correct path, e.g., `mbake -w ./my-site`.
No dependency data recorded yet.