Migrate from Raven / Livqeno

The platform used to have two names: Raven inside the code (package names, class names, the CLI) and Livqeno on the website, the docs and some SDKs. Both are now Livqeno.

This is a rename only. The API, the wire protocols, the tokens and how everything behaves are the same. For most apps the migration is: install the new package names, change your imports, and rename a few environment variables. The old names keep working for now, so you can do it one step at a time.

Package names

npm

Version numbers carry over, so keep the same version ranges.

@ravenkash/effects was removed, not renamed — see Effects removed for what to use instead.

Other languages

The Go module still lives in the atulsinghhhh/swalvo-sdks repository. Only the package directory and package name changed.

Symbol renames

Public names that started with Raven or Livqeno now start with Swalvo.

In TypeScript, Dart and Python the old names are still exported as deprecated aliases of the new ones, so existing code compiles once it points at the new package, and instanceof works with either name. Python also keeps a raven import shim (with a deprecation warning). The aliases will be removed in a future major version. In Go, Java, PHP, Swift and Kotlin the package coordinates changed, so update the imports when you switch.

Docs and examples now name the client variable swalvo (const swalvo = new Swalvo({...})). That's only a convention.

Environment variables

The CLI, and the Go and Java SDKs (for SWALVO_ENV), check SWALVO_* first, then RAVEN_*, then LIVQENO_*. Using an old name prints one deprecation warning per process and never fails.

The TypeScript server SDK reads no environment variables itself, so rename them where your own code reads them: new Swalvo({ apiKey: process.env.SWALVO_API_KEY }).

Webhook headers

See Webhooks for the delivery format.

Every delivery now carries the signature and metadata under the new names, and still under the old ones:

Both carry the same value. The SDK verifiers read swalvo-signature first, then raven-signature (in TypeScript, verifyWebhook also accepts the whole headers object). If you read the header yourself:

const signature = req.header('swalvo-signature') ?? req.header('raven-signature');

The signing scheme (t=<unix>,v1=<hmac-sha256> over "<timestamp>.<raw body>") and your webhook secrets are unchanged.

React CSS classes and custom properties (breaking)

The class names and CSS custom properties that @livqeno/react puts on its components changed prefix:

There are no aliases for these. If your stylesheets target .raven-* selectors, override --raven-* variables, or select on data-raven-* attributes, search for raven- in your CSS and rename it. If you only use the components with their default look, there is nothing to do.

CLI

• The command is now swalvo (swalvo login, swalvo init, …), from @livqeno/cli. The old raven command still works but prints a deprecation notice.
• Settings live in ~/.swalvo/. Any file not there yet is read from ~/.raven/, so you stay logged in. Nothing is moved or deleted.
• swalvo init writes swalvo.json; an existing raven.json is still read.
• In CI, set SWALVO_TOKEN instead of RAVEN_TOKEN.

Domains

Public hostnames move from livqeno.com to livqeno.com:

If you set the API URL yourself (SWALVO_API_URL or a baseUrl option), update it. If you allow-list our hostnames in a Content Security Policy or a firewall, add the livqeno.com ones. Until livqeno.com is live, keep the livqeno.com entries as well.

What did not change

• Error codes keep their RAVEN_ prefix (RAVEN_ROOM_NOT_FOUND, …). Your code matches on them, so they will not be renamed.
• The REST API: paths, bodies and pagination are identical.
• Tokens: same JWTs and claims (aud: raven-rtc, aud: raven-chat). Tokens minted before the rename stay valid until they expire.
• API keys and webhook secrets: nothing to rotate.
• Wire protocols: signaling and chat WebSocket protocols, subprotocol names and data-channel labels are unchanged, so old and new SDKs can share a room.
• End-to-end encryption: key derivation labels are unchanged, so old and new clients can join the same encrypted call.
• On-device storage: offline outbox keys are unchanged.
• Behaviour: rooms, chat, live streaming and limits work as before.

Checklist

1. Swap the packages. Replace every @ravenkash/* dependency with the matching @swalvo/* one (@ravenkash/client → @livqeno/live). For other languages, use the table above.
2. Update imports. Change the import paths. With the deprecated aliases in place this is enough to get the build green.
3. Rename the symbols. Replace Raven*, useRaven* and Livqeno* with Swalvo* and useSwalvo*.
4. Rename environment variables to SWALVO_* in every environment (local .env, CI, staging, production).
5. Webhooks. If you read the signature header yourself, read swalvo-signature first, raven-signature second.
6. CSS. Rename any .raven-* selectors, --raven-* variables and data-raven-* attribute selectors to swalvo.
7. CLI. Install @livqeno/cli, use swalvo in scripts, and set SWALVO_TOKEN in CI.
8. Hostnames. Update any hard-coded livqeno.com URLs and CSP or firewall allow-lists.
9. Leave error code handling alone. RAVEN_* codes stay as they are.
10. Check for warnings. Run your app and look for deprecation warnings about old environment variable names or aliases. When there are none, you're done.