SDKs

Messagevisor SDKs consume generated datafiles and evaluate translations at runtime. They are deliberately small: the CLI builds compact JSON artifacts per target and locale, and SDKs make those artifacts useful inside applications.

Available SDKs#

• JavaScript
• Node.js
• Browser
• React
• Vue
• React Native
• React Intl compatibility

Native SDKs supporting languages like Swift, Python, Java, etc. are coming soon.

What SDKs consume#

SDKs do not read source YAML or JSON definitions directly. They consume built datafiles. Each datafile is target-specific and locale-specific, so applications only load the translations, formats, override logic, and locale metadata they need.

For example:

datafiles/
├── messagevisor-web-en-US.json
└── messagevisor-mobile-nl-NL.json

Once build and deployed, they could be accessible via CDN like cdn.yoursite.com/datafiles/messagevisor-web-en-US.json.

Common runtime concerns#

Most SDK integrations answer the same set of questions:

• which target datafile should this app load?
• which locale is active?
• what context should be passed for overrides and segments?
• which modules are needed for ICU, interpolation, or rich text?
• how should missing translations and warnings be observed?

The JavaScript SDK page explains the core runtime model.

Browser, Node.js, React, Vue, and React Intl compatibility pages build on that same foundation.

Choosing a page#

Start with:

• JavaScript SDK for core APIs and runtime state
• Browser SDK for client-side datafile fetching
• Node.js SDK for server-side rendering or scripts
• React SDK for providers and hooks
• Vue SDK for a Vue plugin, composables, and components
• React Native SDK for mobile apps
• React Intl compatibility for migration from react-intl

Related#

• Evaluation
• Targets
• Modules
• Frameworks
• Deployment