A tool to bundle the client part of a Meteor app into static files for hosting on any server or via file://.
Meteor Build Client is a command-line tool that bundles the client-side portion of a Meteor application into static files. It generates an index.html and associated assets, enabling deployment on any static web server or local file system. This solves the problem of tightly coupling Meteor's client and server, offering greater flexibility in hosting and deployment.
Meteor developers who need to deploy their client applications independently from the Meteor server, such as those wanting to host on static hosting services (like Netlify or GitHub Pages) or load apps via the file:// protocol.
Developers choose this tool because it provides a straightforward way to decouple Meteor's client, allowing static hosting without a Meteor server. Its unique selling point is the ability to configure URLs for server connections or local file usage and integrate Meteor settings, which isn't natively supported in standard Meteor builds.
A tool to bundle the client part of a Meteor app.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Generates index.html and assets deployable on any static server or via file:// protocol, enabling use with services like Netlify or local demos, as emphasized in the README.
Allows setting ROOT_URL for DDP connections to a Meteor server or empty strings for local use, providing control over how the client interacts with backend services.
Supports passing a settings.json file to populate Meteor.settings.public on the client, simplifying configuration management without server overhead.
Can use pre-built Meteor bundles with the --usebuild flag, avoiding redundant meteor build commands and speeding up development workflows.
The README explicitly warns against dynamic imports, limiting modern JavaScript practices like code splitting and lazy loading, which can impact performance for large apps.
Connecting to a Meteor server requires manual DDP setup and code changes, as shown in the examples, adding complexity and potential for errors.
For Blaze projects, the tool restricts placement of <meteor-bundled-js />, complicating setup and requiring workarounds compared to other Meteor templating systems.