Skip to main content

🧱 Installing Bricks

Now that we have a mason.yaml, we can uncomment the "hello" brick (hello: 0.1.0+1):

hello: 0.1.0+1

Then, we can use the get command to install all bricks defined in the nearest parent mason.yaml.

mason get

Running mason get should result in output that looks like:

mason get
✓ Got bricks (22ms)

Running mason get will generate a mason-lock.json which can be tracked in source control when working with versioned bricks (git/hosted).

├── .mason
├── mason-lock.json
└── mason.yaml

Bricks are cached for offline use so running mason get again will resolve the cached bricks:

mason get
✓ Got bricks (10ms)

Use mason upgrade to ignore the lockfile and upgrade to the latest support versions of bricks.