In addition to being a development tool, BLDR provides a way for you to migrate and share your code with your team or within the SFMC community.
bldr package command, bldr will take the following actions:
- Slim down your
.local.manifest.jsonfile by removing the asset details that are not needed to create your assets elsewhere
- If you have a
.sfmc.env.jsonfile, bldr will run the process to update your configuration keys
- Scan all files to locate dependencies within HTML, AMPscript, and SSJS
- Grab all dependencies as needed and replace their spot in your file with the generated bldrIds
- Creates your
Once created, your
.package.manifest.json file can be committed to your public GitHub repository to be distributed.
It's recommended that along with your package file, you create a README.md for the repository with any installation instructions or documentation for the project.
Currently, BLDR supports packaging files for Content Builder and Data Extensions. Extended support for packages will be in development and released in the near future.
Supported Content Builder assets are HTML Emails, HTML Blocks, and Codesnippet Content Blocks.
During the package command, bldr will attempt to find any dependencies in your files. Below is the current list of AMPScript/SSJS functions that will be picked up as dependencies:
Dependency support is a part of bldr that will be constently expanding, to request dependency support submit an issue to the bldr-sfmc-sdk repository.