2 posts tagged with "cli"

Say hello to juno run 👋

Build custom scripts that already know your env, profile & config.
Write them in JS/TS.
Run with the CLI. ⚡️

🍒 on top? Works out of the box in GitHub Actions!

For example:

import { defineRun } from "@junobuild/config";

export const onRun = defineRun(({ mode, profile }) => ({
  run: async ({ satelliteId, identity }) => {
    console.log("Running task with:", {
      mode,
      profile,
      satelliteId: satelliteId.toText(),
      whoami: identity.getPrincipal().toText()
    });
  }
}));

Run it with:

juno run --src ./my-task.ts

Now, let’s suppose you want to fetch a document from your Satellite’s Datastore (“from your canister’s little DB”) and export it to a file:

import { getDoc } from "@junobuild/core";
import { defineRun } from "@junobuild/config";
import { jsonReplacer } from "@dfinity/utils";
import { writeFile } from "node:fs/promises";

export const onRun = defineRun(({ mode }) => ({
  run: async (context) => {
    const key = mode === "staging" ? "123" : "456";

    const doc = await getDoc({
      collection: "demo",
      key,
      satellite: context
    });

    await writeFile("./mydoc.json", JSON.stringify(doc, jsonReplacer, 2));
  }
}));

Fancy ✨

And since it’s TS/JS, you can obviously use any libraries to perform admin tasks as well.

import { defineRun } from "@junobuild/config";
import { IcrcLedgerCanister } from "@dfinity/ledger-icrc";
import { createAgent } from "@dfinity/utils";

export const onRun = defineRun(({ mode }) => ({
  run: async ({ identity, container: host }) => {
    if (mode !== "development") {
      throw new Error("Only for fun!");
    }

    const agent = await createAgent({
      identity,
      host
    });

    const { metadata } = IcrcLedgerCanister.create({
      agent,
      canisterId: MY_LEDGER_CANISTER_ID
    });

    const data = await metadata({});

    console.log(data);
  }
}));

Coolio?

I’ll demo it next Monday in Juno Live. 🎥 https://youtube.com/@junobuild

Happy week-end ☀️

Hi 👋

A new release is out — v0.0.52 🚀

Here are a few highlights:
🧊 Longer default freezing thresholds
✅ Gzipped HTML
🔐 Allowed Callers
🛠 CLI Improvements
🖥 Polished Console UI

Checkout the release notes for details 👉 Release v0.0.52 · junobuild/juno

Let me know if anything looks fishy — and happy coding! 👨‍🔧

🖥️ Two screenshots from the Console new features

The new “Notifications” component:

The overall look: collapsible menu, redesigned tabs, more prominent actions, and more.

As a side note on this release: aside from the custom domain feature, I think it’s now possible to configure your entire project — including authentication, data, storage, and emulator — directly within the Juno config file. Plus with type safety as the cherry on top.

This is especially handy for maintainability or if your project can be forked.

Here’s an example config that shows where and how the project is deployed, which headers to apply to assets, defines the structure of that data, and which image to use when running the emulator with Podman:

import { defineConfig } from "@junobuild/config";

/** @type {import('@junobuild/config').JunoConfig} */
export default defineConfig({
  satellite: {
    ids: {
      development: "jx5yt-yyaaa-aaaal-abzbq-cai",
      production: "fmkjf-bqaaa-aaaal-acpza-cai"
    },
    source: "build",
    predeploy: ["npm run build"],
    storage: {
      headers: [
        {
          source: "**/*.png",
          headers: [["Cache-Control", "max-age=2592000"]]
        }
      ]
    },
    collections: {
      datastore: [
        {
          collection: "notes",
          read: "managed",
          write: "managed",
          memory: "stable"
        }
      ]
    }
  },
  emulator: {
    runner: {
      type: "podman"
    },
    satellite: {}
  }
});

Documentation 👉 https://juno.build/docs/reference/configuration