v0.4.3

Using Bzlmod with Bazel 6 or greater

1. (Bazel 6+ only) Enable with common --enable_bzlmod in .bazelrc.
2. Add to your MODULE.bazel file:

bazel_dep(name = "rules_formatjs", version = "0.4.3")

That's it! The toolchains are automatically registered.

Full Changelog: v0.4.2...v0.4.3

v0.4.2

Using Bzlmod with Bazel 6 or greater

1. (Bazel 6+ only) Enable with common --enable_bzlmod in .bazelrc.
2. Add to your MODULE.bazel file:

bazel_dep(name = "rules_formatjs", version = "0.4.2")

That's it! The toolchains are automatically registered.

Full Changelog: v0.4.1...v0.4.2

v0.4.1

Using Bzlmod with Bazel 6 or greater

1. (Bazel 6+ only) Enable with common --enable_bzlmod in .bazelrc.
2. Add to your MODULE.bazel file:

bazel_dep(name = "rules_formatjs", version = "0.4.1")

That's it! The toolchains are automatically registered.

Full Changelog: v0.4.0...v0.4.1

v0.4.0

Using Bzlmod with Bazel 6 or greater

1. (Bazel 6+ only) Enable with common --enable_bzlmod in .bazelrc.
2. Add to your MODULE.bazel file:

bazel_dep(name = "rules_formatjs", version = "0.4.0")

That's it! The toolchains are automatically registered.

Testing the Installation

A smoke test is included in the release at e2e/smoke/. To verify the rules work in your environment:

cd e2e/smoke
bazel build //:extract

This will extract messages from a simple React component and verify that the FormatJS CLI toolchain is working correctly.

What's Changed

• chore(deps): update dependency rules_shell to v0.6.1 by @renovate[bot] in #25
• chore(deps): update dependency oxfmt to ^0.23.0 by @renovate[bot] in #21

Full Changelog: v0.3.0...v0.4.0

v0.3.0

Using Bzlmod with Bazel 6 or greater

1. (Bazel 6+ only) Enable with common --enable_bzlmod in .bazelrc.
2. Add to your MODULE.bazel file:

bazel_dep(name = "rules_formatjs", version = "0.3.0")

That's it! The toolchains are automatically registered.

Testing the Installation

A smoke test is included in the release at e2e/smoke/. To verify the rules work in your environment:

cd e2e/smoke
bazel build //:extract

This will extract messages from a simple React component and verify that the FormatJS CLI toolchain is working correctly.

What's Changed

• fix: add e2e/smoke to tar so bcr presubmit can run by @longlho in #20
• feat: allow aggregate to output to specific file by @longlho in #22
• fix: remove rules_shell dep by @longlho in #23
• feat: allow custom formatjs_cli toolchain by @longlho in #24

Full Changelog: v0.2.4...v0.3.0

v0.2.4

Using Bzlmod with Bazel 6 or greater

1. (Bazel 6+ only) Enable with common --enable_bzlmod in .bazelrc.
2. Add to your MODULE.bazel file:

bazel_dep(name = "rules_formatjs", version = "0.2.4")

That's it! The toolchains are automatically registered.

Full Changelog: v0.2.3...v0.2.4

v0.2.3

Using Bzlmod with Bazel 6 or greater

1. (Bazel 6+ only) Enable with common --enable_bzlmod in .bazelrc.
2. Add to your MODULE.bazel file:

bazel_dep(name = "rules_formatjs", version = "0.2.3")

That's it! The toolchains are automatically registered.

Full Changelog: v0.2.2...v0.2.3

v0.2.2

Using Bzlmod with Bazel 6 or greater

1. (Bazel 6+ only) Enable with common --enable_bzlmod in .bazelrc.
2. Add to your MODULE.bazel file:

bazel_dep(name = "rules_formatjs", version = "0.2.2")

bazel_dep(name = "aspect_bazel_lib", version = "2.22.2")

**Full Changelog**: https://github.com/formatjs/rules_formatjs/compare/v0.2.1...v0.2.2

v0.2.1

Using Bzlmod with Bazel 6 or greater

1. (Bazel 6+ only) Enable with common --enable_bzlmod in .bazelrc.
2. Add to your MODULE.bazel file:

bazel_dep(name = "rules_formatjs", version = "0.2.1")

bazel_dep(name = "aspect_bazel_lib", version = "2.22.2")

**Full Changelog**: https://github.com/formatjs/rules_formatjs/compare/v0.2.0...v0.2.1