Packaging & Versioning

Once you've finished developing and testing your blocklet, the next step is to prepare it for distribution. This involves two critical processes: versioning, to assign a unique identifier to your release, and bundling, to package all your code and assets into a single, deployable artifact. The Blocklet CLI provides dedicated commands to streamline this workflow.
This section provides an overview of the commands used to package and version your blocklet. For detailed instructions, please refer to the specific sub-pages.
Bundle Blocklet
Learn how to use the `blocklet bundle` command to package your project. The CLI intelligently selects the best bundling mode (zip, simple, or compact) based on your blocklet's configuration, ensuring an optimized package for deployment.
Manage Version
Discover how the `blocklet version` command helps you manage your project's version number following semantic versioning (semver) standards. Properly versioning your blocklet is essential for release management and dependency tracking.
Typical Workflow#The packaging and versioning process is a straightforward part of the development lifecycle, typically occurring after development and before distribution.

After successfully bundling your blocklet with an updated version, you are ready to share it with the world.
Proceed to the Distribution section to learn how to deploy your blocklet to a server or upload it to a blocklet store.

Overview

Getting Started

Server Management

Blocklet Workflows

Configuration

Advanced Topics

Command Reference

Environment Variables

Packaging & Versioning

Bundle Blocklet

Manage Version

Typical Workflow#

Component Studio CLI

Bundle Blocklet