Version Packages [skip preview]

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@inlang/[email protected]

Major Changes

• 7791be7: Upgraded the inlang SDK to Lix v0.5 🎉

  Highlights

  Writing directly to Lix state

  State is now written straight into Lix instead of the SDK’s private in-memory SQLite snapshot. Every bundle, message, and variant change becomes a first-class Lix commit, unlocking:

  • history and branching,
  • writer-key aware workflows,
  • change proposals and subscriptions, and
  • a single source of truth for downstream tools.

  Per-file filesystem sync

  Any inlang-based tooling that opens a project from disk (IDE extensions, CLIs, custom apps) used to patch the entire locale tree whenever a single message changed. That behaviour is at the heart of opral/inlang-sherlock#173 where editing one key in en.json would re-export every other locale file, destroying manual formatting or reintroducing stale content.

  Thanks to Lix v0.5’s observable state and writer-key APIs we can now react to per-commit metadata and suppress our own writes. When happy_elephant in en.json is updated, the SDK marks only en.json as dirty, leaving de.json and friends untouched. Drift is still possible if another tool rewrites en.json, yet the blast radius falls from “the whole project just changed” to “only the file you touched,” making reviews and merges manageable across all inlang integrations.

@inlang/[email protected]

Minor Changes

• ff07482: Require the INLANG_GOOGLE_TRANSLATE_API_KEY environment variable for machine translations.

  We previously subsidized machine translation costs. As projects become larger, our bill is no longer sustainable.

  To ensure that machine translations remain available, we are switching to a Bring Your Own Key (BYOK) model.

  Before

  npx @inlang/cli machine translate --project ./project.inlang

  After

  export INLANG_GOOGLE_TRANSLATE_API_KEY="your-google-api-key"
  npx @inlang/cli machine translate --project ./project.inlang

• 7791be7: Upgraded the inlang SDK to Lix v0.5 🎉

  Highlights

  Writing directly to Lix state

  State is now written straight into Lix instead of the SDK’s private in-memory SQLite snapshot. Every bundle, message, and variant change becomes a first-class Lix commit, unlocking:

  • history and branching,
  • writer-key aware workflows,
  • change proposals and subscriptions, and
  • a single source of truth for downstream tools.

  Per-file filesystem sync

  Any inlang-based tooling that opens a project from disk (IDE extensions, CLIs, custom apps) used to patch the entire locale tree whenever a single message changed. That behaviour is at the heart of opral/inlang-sherlock#173 where editing one key in en.json would re-export every other locale file, destroying manual formatting or reintroducing stale content.

  Thanks to Lix v0.5’s observable state and writer-key APIs we can now react to per-commit metadata and suppress our own writes. When happy_elephant in en.json is updated, the SDK marks only en.json as dirty, leaving de.json and friends untouched. Drift is still possible if another tool rewrites en.json, yet the blast radius falls from “the whole project just changed” to “only the file you touched,” making reviews and merges manageable across all inlang integrations.

Patch Changes

• 930df2d: Fix CLI build banner to avoid duplicate createRequire declarations when bundling SQLite from lix.
• Updated dependencies [7791be7]
  • @inlang/[email protected]

@inlang/[email protected]

Minor Changes

• 7791be7: Upgraded the inlang SDK to Lix v0.5 🎉

  Highlights

  Writing directly to Lix state

  State is now written straight into Lix instead of the SDK’s private in-memory SQLite snapshot. Every bundle, message, and variant change becomes a first-class Lix commit, unlocking:

  • history and branching,
  • writer-key aware workflows,
  • change proposals and subscriptions, and
  • a single source of truth for downstream tools.

  Per-file filesystem sync

  Any inlang-based tooling that opens a project from disk (IDE extensions, CLIs, custom apps) used to patch the entire locale tree whenever a single message changed. That behaviour is at the heart of opral/inlang-sherlock#173 where editing one key in en.json would re-export every other locale file, destroying manual formatting or reintroducing stale content.

  Thanks to Lix v0.5’s observable state and writer-key APIs we can now react to per-commit metadata and suppress our own writes. When happy_elephant in en.json is updated, the SDK marks only en.json as dirty, leaving de.json and friends untouched. Drift is still possible if another tool rewrites en.json, yet the blast radius falls from “the whole project just changed” to “only the file you touched,” making reviews and merges manageable across all inlang integrations.

Patch Changes

• 72d1c53: Ensure the CLI honours allowJs flags defined in extended or referenced tsconfig files instead of prompting unnecessarily.

  Refs Add Configuration Option to Use Existing Translation Files as Source of Truth inlang-paraglide-js#560.

• 9735b82: Fix fallback assignment generation so locale chains emit dependencies first and avoid "Block-scoped variable used before its declaration" errors. See ts error "Block-scoped variable used before its declaration." inlang-paraglide-js#507 for details.

• Updated dependencies [7791be7]

  • @inlang/[email protected]

@lix-js/[email protected]

Minor Changes

• b785bbd: Switch HTML diff parsing from the browser-only DOMParser to server-friendly parse5 so the library can run in Node, workers, and other isomorphic environments without DOM shims.

@inlang/[email protected]

Patch Changes

• Updated dependencies [7791be7]
  • @inlang/[email protected]

@inlang/[email protected]

Patch Changes

• Updated dependencies [7791be7]
  • @inlang/[email protected]

@inlang/[email protected]

Patch Changes

• Updated dependencies [7791be7]
  • @inlang/[email protected]

@inlang/[email protected]

Patch Changes

• Updated dependencies [7791be7]
  • @inlang/[email protected]

@inlang/[email protected]

Patch Changes

• Updated dependencies [7791be7]
  • @inlang/[email protected]

[email protected]

Minor Changes

• 9a65cb4: Add centralized Sherlock logging so activation and project loading diagnostics are visible in the VS Code output tab, refine the direct message watcher to stop self-saving loops, make the editor webview always load bundled assets, and debounce editor writes while still saving projects to disk.

Patch Changes

• b428890: Switch the Sherlock message sidebar from a polling loop to the new lix.observe API so bundle updates stream in immediately without hammering the database during activation.
• Updated dependencies [7791be7]
  • @inlang/[email protected]
  • @inlang/[email protected]
  • @inlang/[email protected]
  • @inlang/[email protected]

@inlang/[email protected]

Patch Changes

• Updated dependencies [7791be7]
  • @inlang/[email protected]

[email protected]

Patch Changes

• @inlang/[email protected]

@opral/[email protected]

Patch Changes

• @lix-js/[email protected]
• @lix-js/[email protected]

@lix-js/[email protected]

Patch Changes

• [email protected]

@lix-js/[email protected]

Patch Changes

• Updated dependencies [b785bbd]
  • @lix-js/[email protected]

[email protected]

Patch Changes

• @lix-js/[email protected]