Each valdi module contains a BUILD.bazel file which has a single call to valdi_module macros. The macro setups a few targets and aliases to build the module from source using the Valdi Toolchain.

The list of targets created by the valdi_module macro includes:

• module_name:module_name target which builds just the .valdimodule file. It is the default target and can be referenced as module_name for example //src/valdi_modules/src/valdi/jasmine.
• module_name:module_name_kt target which builds the android_library and packages the Valdi generated Kotlin code, if any. It depends on the Valdi module target above and adds the .valdimodule and other resources to the data attribute.
• module_name:module_name_objc target which builds the objc_library and packages the Valdi generated Objective-C code, if any. It depends on the Valdi module target above and adds the .valdimodule and other resources to the data attribute.
• module_name:module_name_objc_api target which builds the objc_library and wraps the generated Objective-C API code, if any. It also depends on the module_name_objc target above.
• module_name:{ModuleName} an alias pointing at module_name:module_name_objc to keep the compatibility with iOS
• module_name:{ModuleName}Types an alias pointing at module_name:module_name_objc_api to keep the compatibility with iOS

To build a single module using the default, macOS toolchain:

bazel build //src/valdi_modules/src/valdi/jasmine

To build the Android target:

bazel build //src/valdi_modules/src/valdi/jasmine --platforms=@snap_platforms//os:android_arm64

To build the iOS target:

bazel build //src/valdi_modules/src/valdi/jasmine --platforms=//bzl/platforms:ios_x64

A Valdi module is configured entirely through the valdi_module(...) call in its BUILD.bazel. Edit that file directly to change module configuration.

To add a new dependency, add the module's Bazel label to the deps attribute of the valdi_module() call in BUILD.bazel. For example:

valdi_module(
    name = "my_module",
    srcs = glob(["src/**/*.ts", "src/**/*.tsx"]),
    deps = [
        "@valdi//src/valdi_modules/src/valdi/valdi_core",
        "//src/valdi_modules/src/valdi/some_other_valdi_module",
    ],
)

See Core Module for the full list of valdi_module() attributes.

Note: Older Valdi projects may have a module.yaml file alongside BUILD.bazel. module.yaml is deprecated; all module configuration belongs in the valdi_module() rule. See glossary.

You can run your tests using bazel test directly. See documentation about it here: Testing.

Once implemented, users will be able to run linting for a single module using Bazel.

By default, Bazel uses the prebuilt compiler and builds the companion from source (the companion is the JS/TS app in compiler/companion). To use your own builds so they are not overwritten by prebuilts:

1. Build the Valdi compiler and place the binary where the toolchain can find it:

   compiler/compiler/scripts/update_compiler_bazel.sh -o compiler/compiler/out

   This produces compiler/compiler/out/macos/valdi_compiler (or out/linux/valdi_compiler on Linux). The compiler is built with Bazel (//compiler/compiler:local_valdi_compiler), so no Swift toolchain install is required. The script works in both the mirrored public repo and the mobile monorepo.

2. Build Valdi modules with the local compiler:

   bazel build //src/valdi_modules/src/valdi/jasmine --//bzl/valdi:use_local_compiler=true

The out/ directory is gitignored so your local binary is never committed.

cat "$(ls ~/.cache/bazel/*/bazel-workers/worker-*-ValdiCompile.log 2>/dev/null | head -1)"

The toolchain already uses the source-built companion by default (use_prebuilt_companion is false), so the companion is built from compiler/companion (e.g. webpack output). To avoid Bazel overwriting your npm-built companion output:

1. Build the companion in dev mode (writes to dist_dev/ instead of dist/):

   cd compiler/companion && npm run build-dev

2. Build or run Valdi with the dev-mode companion:

   bazel build //src/valdi_modules/src/valdi/jasmine --//compiler/companion:dev_mode=true

Bazel will use dist_dev/bundle.js and will not overwrite your dist/ folder.

• Updating proto config doesn't trigger a valdi module rebuild