Migration Guide

Explicit Public Exports

The package now declares an explicit public exports map. Documented top-level imports continue to work:

import { lookupErrorCode, translateErrorCode } from 'supabase-error-translator-js';

New public translation subpaths are available:

import { translations } from 'supabase-error-translator-js/translations';
import de from 'supabase-error-translator-js/translations/de';

Undocumented deep imports, such as importing files from dist/ directly through the package name, are not supported by the public API and may be blocked by the exports map. Use the top-level package import or the documented translations subpaths instead.

From v2 To v3

Version 3 uses ISO 639-1 language codes for Japanese, Korean, and Chinese.

Update calls like this:

import { setLanguage } from 'supabase-error-translator-js';

setLanguage('ja');
setLanguage('ko');
setLanguage('zh');

translateErrorCode() without a lang argument now uses the language set by setLanguage() instead of always trying browser detection.

From v1 To v2

Version 2 added service-specific translation maps. translateErrorCode() now requires a service argument.

import { translateErrorCode } from 'supabase-error-translator-js';

// v1
translateErrorCode('invalid_credentials');

// v2 and newer
translateErrorCode('invalid_credentials', 'auth');

Choose the service from the Supabase API that produced the error.