@dialpad/i18n 1.22.3 → 1.24.0

package/dist/types/index.d.ts

@@ -1,4 +1,2 @@
-export type { LocaleCode, NamespaceCode, ResourceKey, LocaleManagerParams, SetLocaleParams, UseI18N, } from '@dialpad/i18n-services/locale-manager';
-export type { BundleSource } from '@dialpad/i18n-services/bundle-source';
-export { LocaleManager, useI18N, INJECTION_KEY_PREFIX, } from './src/locale-manager';
-export { HTTPBundleSource, RawBundleSource, } from '@dialpad/i18n-services/bundle-source';
+export type { LocaleCode, NamespaceCode, ResourceKey, LocaleManagerParams, SetLocaleParams, UseI18N, FluentFormat, FluentFormatAttrs, UniversalRef, BundleSource, Resource, BuiltResource, FTLModule, HTTPBundleSourceParams, RawBundleSourceParams, StorageWrapper, } from '@dialpad/i18n-goblin-core';
+export { BaseLocaleManager, LocaleManager, useI18N, findLocaleManager, globalLocaleManagers, INJECTION_KEY_PREFIX, HTTPBundleSource, RawBundleSource, createStorageWrapper, MemoryStorageWrapper, } from '@dialpad/i18n-goblin-core';

package/dist/types/index.js

@@ -1,2 +1 @@
-export { LocaleManager, useI18N, INJECTION_KEY_PREFIX, } from './src/locale-manager';
-export { HTTPBundleSource, RawBundleSource, } from '@dialpad/i18n-services/bundle-source';
+export { BaseLocaleManager, LocaleManager, useI18N, findLocaleManager, globalLocaleManagers, INJECTION_KEY_PREFIX, HTTPBundleSource, RawBundleSource, createStorageWrapper, MemoryStorageWrapper, } from '@dialpad/i18n-goblin-core';

package/{README.md → docs/README.md}

@@ -1,14 +1,16 @@
+<!-- @docsite-text: Internationalization -->
+
 # i18n (Vue 3 compatible)
 
 ## Introduction
 
-This package contains all the logic needed to take care the i18n of a Dialpad
+This package contains all the logic needed to handle i18n for a Dialpad
 application extending from the common logic existing in the base locale manager
 that you can find about on the
-[i18n-services documentation](../i18n-services/README.md), based on different
-bundle sources.
+[i18n-services documentation](../../i18n-services/docs/README.md), based on
+different bundle sources.
 
-## How it works?
+## How it works
 
 There are essentially two main concepts behind the scenes:
 
@@ -46,31 +48,27 @@ different use cases.
   efficient access while still being flexible enough to load translations on
   demand.
 
-**Disclaimer:** _Both implementations are provisional and may change as we
-better understand our needs. Currently, `RawBundleSource` is the preferred
-option for most applications._
+**Note:** Both implementations are provisional and may change. Currently,
+`RawBundleSource` is the preferred option for most applications.
 
-#### Synchronous Resource Loading with [builtResources](cci:1://file:///Users/daniellovero/src/web-clients/packages/i18n-services/bundle/bundle-source/raw.js:28:2-34:3)
+#### Synchronous Resource Loading with [builtResources](../../i18n-goblin-core/src/bundle-source)
 
-While the
-[dynamicResources](cci:1://file:///Users/daniellovero/src/web-clients/packages/i18n-services/bundle/bundle-source/raw.js:2:2-17:3)
-method is used for asynchronously loading resources, the
-[RawBundleSource](cci:2://file:///Users/daniellovero/src/web-clients/packages/i18n-services/bundle/bundle-source/raw.d.ts:14:0-30:1)
-class also provides a
-[builtResources](cci:1://file:///Users/daniellovero/src/web-clients/packages/i18n-services/bundle/bundle-source/raw.js:28:2-34:3)
-method for synchronous resource loading. This is useful when you have the
-localization resources available at compile time and prefer to import them
-directly without dealing with promises.
+While the [dynamicResources](../../i18n-goblin-core/src/bundle-source) method is
+used for asynchronously loading resources, the
+[RawBundleSource](../../i18n-goblin-core/src/bundle-source) class also provides
+a [builtResources](../../i18n-goblin-core/src/bundle-source) method for
+synchronous resource loading. This is useful when you have the localization
+resources available at compile time and prefer to import them directly without
+dealing with promises.
 
-##### How to use [builtResources](cci:1://file:///Users/daniellovero/src/web-clients/packages/i18n-services/bundle/bundle-source/raw.js:28:2-34:3)
+##### How to use [builtResources](../../i18n-goblin-core/src/bundle-source)
 
 Instead of dynamically importing `.ftl` files, you can import them directly and
-use the
-[builtResources](cci:1://file:///Users/daniellovero/src/web-clients/packages/i18n-services/bundle/bundle-source/raw.js:28:2-34:3)
-method to process the resources. Here's an example:
+use the [builtResources](../../i18n-goblin-core/src/bundle-source) method to
+process the resources. Here's an example:
 
 ```typescript
-import { RawBundleSource } from '@dialpad/i18n-services';
+import { RawBundleSource } from '@dialpad/i18n';
 // Import your .ftl files directly
 import enUSResource from './locales/en-US.ftl';
 import esResource from './locales/es.ftl';
@@ -100,23 +98,22 @@ pnpm add @dialpad/i18n
 
 ### Configuration - Static resources
 
-### Integrating LocaleManager with Vue using the [install](cci:1://file:///Users/daniellovero/src/web-clients/packages/i18n-vue2/src/locale-manager.ts:43:2-55:3) Method
+### Integrating LocaleManager with Vue using the [install](../../i18n-goblin-core/src/locale-manager) Method
 
 When using `LocaleManager` within a Vue application, **(especially in the
 context of a library, you should be aware that install needs to receive a
 non-default namespace value)** it's important to properly integrate it using the
-[install](cci:1://file:///Users/daniellovero/src/web-clients/packages/i18n-vue2/src/locale-manager.ts:43:2-55:3)
-method. This method registers `LocaleManager` with the Vue instance, allowing
-for global access to localization functionalities across the application.
+[install](../../i18n-goblin-core/src/locale-manager) method. This method
+registers `LocaleManager` with the Vue instance, allowing for global access to
+localization functionalities across the application.
 
-#### Usage of [install](cci:1://file:///Users/daniellovero/src/web-clients/packages/i18n-vue2/src/locale-manager.ts:43:2-55:3)
+#### Usage of [install](../../i18n-goblin-core/src/locale-manager)
 
 After creating an instance of `LocaleManager`, you must call the
-[install](cci:1://file:///Users/daniellovero/src/web-clients/packages/i18n-vue2/src/locale-manager.ts:43:2-55:3)
-method. This method accepts an optional `namespace` parameter, which is
-particularly useful when you are developing a library and need to avoid
-conflicts with other potential instances of `LocaleManager` in the consumer's
-environment.
+[install](../../i18n-goblin-core/src/locale-manager) method. This method accepts
+an optional `namespace` parameter, which is particularly useful when you are
+developing a library and need to avoid conflicts with other potential instances
+of `LocaleManager` in the consumer's environment.
 
 By using different namespaces, you can have multiple instances of
 `LocaleManager` available globally in Vue. This is ideal for libraries that may
@@ -131,8 +128,8 @@ scoped localization management is required.
 ##### Example
 
 ```typescript
-import Vue from 'vue';
-import { LocaleManager } from '@dialpad/i18n-vue2';
+import { createApp } from 'vue';
+import { LocaleManager } from '@dialpad/i18n';
 
 // Create a LocaleManager instance with your configuration options
 const localeManager = new LocaleManager({
@@ -142,16 +139,17 @@ const localeManager = new LocaleManager({
 // Install the LocaleManager with a specific namespace to avoid conflicts
 localeManager.install('my-namespace');
 
-// Your library's users can now access the LocaleManager instance globally in Vue
-new Vue({
-  // ... other options
-}).$mount('#app');
+// Your app's users can now access the LocaleManager instance globally in Vue
+const app = createApp({
+  /* ... */
+});
+app.mount('#app');
 ```
 
 ### Configuration - Dynamic resources
 
-We recommend you to include this in your own composable that handle every locale
-and i18n set up logic, i.e.:
+You should include this in your own composable that handles locale and i18n
+setup logic, for example:
 
 ```ts
 //src/localization/i18n.ts
@@ -183,11 +181,11 @@ export async function hostI18NManager({
 }
 ```
 
-**Important note:** let's say that you have more than one `allowedLocales`, or
-that your `fallbackLocale`/`preferredLocale` is different from what you're
-specifying on the `allowedLocales` prop to the `LocaleManager` instance. In
-those cases you need to verify that you have specified a Bundle resource for
-each locale, in order to have them working properly, i.e.:
+**Important note:** If you have more than one `allowedLocales`, or if your
+`fallbackLocale`/`preferredLocale` is different from what you're specifying on
+the `allowedLocales` prop to the `LocaleManager` instance, in those cases, you
+need to verify that you have specified a Bundle resource for each locale for
+them to work properly. For example:
 
 ```ts
 //src/localization/i18n.ts
@@ -223,6 +221,116 @@ export async function hostI18NManager({
 }
 ```
 
+### Configuration - Multiple namespaces
+
+For larger applications, having a single `en-US.ftl` file may not scale well.
+You can split your translations across multiple `.ftl` files by using different
+**namespaces**. Each resource maps to a unique `[locale, namespace]` pair, so
+you can organize translations per feature, module, or component.
+
+```ts
+//src/localization/i18n.ts
+import type { App } from 'vue';
+import { LocaleManager, RawBundleSource } from '@dialpad/i18n';
+
+export async function hostI18NManager({
+  vueApp,
+}: {
+  vueApp: App;
+}): Promise<void> {
+  const bundleSource = new RawBundleSource({
+    resources: await RawBundleSource.dynamicResources([
+      // One .ftl file per feature/module, each with its own namespace
+      ['en-US', 'feature-chat', import('./chat/en-US.ftl?raw')],
+      ['en-US', 'feature-settings', import('./settings/en-US.ftl?raw')],
+      ['en-US', 'feature-contacts', import('./contacts/en-US.ftl?raw')],
+    ]),
+  });
+
+  const manager = new LocaleManager({
+    bundleSource,
+    fallbackLocale: 'en-US',
+    // List all namespaces used above
+    namespaces: ['feature-chat', 'feature-settings', 'feature-contacts'],
+  });
+
+  await manager.ready;
+
+  vueApp.use(manager);
+}
+```
+
+Given the following `.ftl` files per feature:
+
+```ftl
+# src/localization/chat/en-US.ftl
+CHAT_TITLE = Chat
+CHAT_SEND_BUTTON =
+  .aria-label = Send message
+  .title = Send
+CHAT_INPUT_PLACEHOLDER = Type a message...
+```
+
+```ftl
+# src/localization/contacts/en-US.ftl
+CONTACTS_TITLE = Contacts
+CONTACTS_SEARCH_PLACEHOLDER = Search contacts...
+```
+
+You can then use `useI18N` with the corresponding namespace in your Vue
+components:
+
+```vue
+<script setup lang="ts">
+// Pass the namespace to useI18N to get translations from a specific .ftl file
+import { useI18N } from '@dialpad/i18n';
+
+const { $t, $ta } = useI18N('feature-chat');
+</script>
+
+<template>
+  <div>
+    <h1>{{ $t('CHAT_TITLE') }}</h1>
+    <input :placeholder="$t('CHAT_INPUT_PLACEHOLDER')" />
+    <button v-bind="$ta('CHAT_SEND_BUTTON')" />
+  </div>
+</template>
+```
+
+```vue
+<script setup lang="ts">
+import { useI18N } from '@dialpad/i18n';
+
+const { $t } = useI18N('feature-contacts');
+</script>
+
+<template>
+  <div>
+    <h1>{{ $t('CONTACTS_TITLE') }}</h1>
+    <input :placeholder="$t('CONTACTS_SEARCH_PLACEHOLDER')" />
+  </div>
+</template>
+```
+
+> **Tip:** If your app only uses a single namespace (the common case for smaller
+> apps), you can omit the namespace parameter — `useI18N()` defaults to
+> `'default'`.
+
+You can also add resources at runtime using `addSources`, which is useful for
+lazy-loading translations for features that are not immediately needed:
+
+```ts
+// Later, when loading a new feature dynamically
+manager.addSources([
+  ['en-US', 'feature-analytics', analyticsTranslationSource],
+]);
+```
+
+> **Note:** Each `[locale, namespace]` combination must be unique. Providing the
+> same pair twice will throw an error. If you need multiple locales per
+> namespace, provide one resource per locale as shown in the
+> [Dynamic resources](#configuration---dynamic-resources) examples above.
+
 After this, you should plug this into your `main.ts`. You will call it like:
 
 ```ts
@@ -244,7 +352,7 @@ await createHost(hostEnv)
 ### User's locale selection criteria
 
 You will find that this API is (and should always be) the same as the
-[i18n-vue2 tool](../i18n-vue2/README.md).
+[i18n-vue2 tool](../../i18n-vue2/docs/README.md).
 
 When instantiating the LocaleManager (or when calling setI18N), the
 preferredLocale and allowedLocales parameters are optional. BUT this is the
@@ -254,7 +362,7 @@ If preferredLocale param is provided, use that. If allowedLocales param is
 provided, use the first one. If localStorage contains the previously-used value,
 use that. If navigator.language is available, use that. Use the fallbackLocale.
 
-First of all you need to understand he difference between `$t` and `$ta`, which
+First, you need to understand the difference between `$t` and `$ta`, which
 mainly lies in their outputs:
 
 ### useI18N() hook API
@@ -392,53 +500,47 @@ const { setI18N, allowedLocales, currentLocale } = useI18N();
 </template>
 ```
 
-### Dynamically Changing Locales with [changeLocale](cci:1://file:///Users/daniellovero/src/web-clients/packages/i18n-vue2/src/locale-manager.ts:64:2-88:3) Method
+### Dynamically Changing Locales with [changeLocale](../../i18n-goblin-core/src/locale-manager) Method
 
-The
-[changeLocale](cci:1://file:///Users/daniellovero/src/web-clients/packages/i18n-vue2/src/locale-manager.ts:64:2-88:3)
-method provides the functionality to dynamically change the current locale of
-your application. This method can target a specific
-[LocaleManager](cci:2://file:///Users/daniellovero/src/web-clients/packages/i18n-vue2/src/locale-manager.ts:21:0-89:1)
-by namespace or all
-[LocaleManager](cci:2://file:///Users/daniellovero/src/web-clients/packages/i18n-vue2/src/locale-manager.ts:21:0-89:1)
-instances globally.
+The [changeLocale](../../i18n-goblin-core/src/locale-manager) method provides
+the functionality to dynamically change the current locale of your application.
+This method can target a specific
+[LocaleManager](../../i18n-goblin-core/src/locale-manager) by namespace or all
+[LocaleManager](../../i18n-goblin-core/src/locale-manager) instances globally.
 
 #### changeLocale()
 
 To change the locale settings, call the
-[changeLocale](cci:1://file:///Users/daniellovero/src/web-clients/packages/i18n-vue2/src/locale-manager.ts:64:2-88:3)
-method on your
-[LocaleManager](cci:2://file:///Users/daniellovero/src/web-clients/packages/i18n-vue2/src/locale-manager.ts:21:0-89:1)
-instance. You can pass optional parameters to update the locale settings and
-optionally specify a namespace to target a specific
-[LocaleManager](cci:2://file:///Users/daniellovero/src/web-clients/packages/i18n-vue2/src/locale-manager.ts:21:0-89:1).
-If no namespace is provided, the locale settings will be updated for all
-[LocaleManager](cci:2://file:///Users/daniellovero/src/web-clients/packages/i18n-vue2/src/locale-manager.ts:21:0-89:1)
-instances.
+[changeLocale](../../i18n-goblin-core/src/locale-manager) method on your
+[LocaleManager](../../i18n-goblin-core/src/locale-manager) instance. You can
+pass optional parameters to update the locale settings and optionally specify a
+namespace to target a specific
+[LocaleManager](../../i18n-goblin-core/src/locale-manager). If no namespace is
+provided, the locale settings will be updated for all
+[LocaleManager](../../i18n-goblin-core/src/locale-manager) instances.
 
 ##### Parameters
 
 - `args`: (Optional) A `Partial<SetLocaleParams>` object containing the new
   locale settings to be applied.
 - `namespace`: (Optional) The namespace of the
-  [LocaleManager](cci:2://file:///Users/daniellovero/src/web-clients/packages/i18n-vue2/src/locale-manager.ts:21:0-89:1)
-  instance whose locale settings you want to change. If not provided, all
-  instances will be updated.
+  [LocaleManager](../../i18n-goblin-core/src/locale-manager) instance whose
+  locale settings you want to change. If not provided, all instances will be
+  updated.
 
 ###### Behavior
 
 - Retrieves the map of
-  [LocaleManager](cci:2://file:///Users/daniellovero/src/web-clients/packages/i18n-vue2/src/locale-manager.ts:21:0-89:1)
-  instances from the Vue prototype.
+  [LocaleManager](../../i18n-goblin-core/src/locale-manager) instances from the
+  Vue prototype.
 - If a namespace is specified, it targets the corresponding
-  [LocaleManager](cci:2://file:///Users/daniellovero/src/web-clients/packages/i18n-vue2/src/locale-manager.ts:21:0-89:1)
-  and throws an error if it does not exist.
+  [LocaleManager](../../i18n-goblin-core/src/locale-manager) and throws an error
+  if it does not exist.
 - If no namespace is specified, it targets all registered
-  [LocaleManager](cci:2://file:///Users/daniellovero/src/web-clients/packages/i18n-vue2/src/locale-manager.ts:21:0-89:1)
-  instances.
+  [LocaleManager](../../i18n-goblin-core/src/locale-manager) instances.
 - Updates the locale settings for the targeted
-  [LocaleManager](cci:2://file:///Users/daniellovero/src/web-clients/packages/i18n-vue2/src/locale-manager.ts:21:0-89:1)(s)
-  using the provided arguments.
+  [LocaleManager](../../i18n-goblin-core/src/locale-manager)(s) using the
+  provided arguments.
 
 ###### Example
 
@@ -451,12 +553,6 @@ manager.changeLocale({ preferredLocale: 'fr-FR' }, 'myNamespace');
 
 // To change the locale settings for all LocaleManager instances
 manager.changeLocale({ preferredLocale: 'fr-FR' });
-
-### Adding Resources at Runtime with `addSources`
-
-#### API Method: `addSources`
-
-The `addSources` method allows you to add multiple translation resources to the `LocaleManager` at runtime. Once all resources are loaded, it triggers the `ready` promise indicating that the locale manager is fully initialized and ready to handle localization requests.
 ```
 
 ### Adding Resources at Runtime with `addSources`
@@ -494,6 +590,106 @@ const resourcesToAdd: BuiltResource[] = [
 manager.addSources(resourcesToAdd);
 ```
 
+## CLI Tools
+
+`@dialpad/i18n` exposes the following CLI scripts as bin commands. You can run
+them directly with your package manager (e.g. `pnpm exec <command>` or
+`npx <command>`):
+
+| Command                         | Description                                                        |
+| ------------------------------- | ------------------------------------------------------------------ |
+| `translate-dialpadistan`        | Converts an `en-US.ftl` file into a `dp-DP.ftl` file               |
+| `pull-translations`             | Pulls published translations from Smartling                        |
+| `force-pull-translations`       | Force-pulls latest translations without waiting for job completion |
+| `upload-translation-service`    | Pushes `en-US.ftl` source files to Smartling                       |
+| `translation-screenshots-check` | Checks that context screenshots exist for all translation keys     |
+| `should-pull`                   | Checks whether translations should be pulled                       |
+
+### Dialpadistan translator
+
+This feature uses the `@fluent/syntax` parser and a set of regex and grammar
+rules to convert an `en-US.ftl` file into a `dp-DP.ftl` inside the same
+directory. The "dialpadistani" language replaces each Latin character with a
+non-Latin equivalent, which is useful for testing proper rendering of different
+fonts.
+
+For example:
+
+```ftl
+# src/localization/en-US.ftl
+
+MESSAGE_INPUT_LABEL = New message input
+FEED_NEW_SEPARATOR = Beginning of unread items
+```
+
+Will translate to:
+
+```ftl
+# src/localization/dp-DP.ftl
+
+MESSAGE_INPUT_LABEL = Ŋάŵ ɱάššëğά īŋþø†
+FEED_NEW_SEPARATOR = Sάğīŋŋīŋğ ůƒ øŋřάëḍ ī†άɱš
+```
+
+To execute a Dialpadistan translation you should run the following script
+pointing to your Fluent English file: _(Note: it can either be a relative path
+or an absolute path)_
+
+```sh
+pnpm exec translate-dialpadistan /your/english/fluent/file/en-US.ftl
+```
+
+After a successful translation, a message appears in your terminal indicating
+where the output file was placed. The output folder is _the same as your English
+Fluent file_.
+
+e.g. in this case you will see
+`File transformed and saved as /your/english/fluent/file/dp-DP.ftl`.
+
+#### Known issues
+
+There is one specific scenario where this translator is failing, and we don't
+consider it to be harmful. This is because of a bug on `@fluent/syntax` parser.
+
+And this is when having a comment right in the middle between an equal sign and
+a value, and that comment has at least one placeholder, whatever's after the
+text of the first placeholder will be translated (and if the comment it's
+multi-lined every comment line will be squashed and inlined after that
+placeholder as well)
+
+e.g.
+
+```ftl
+MY_KEY =
+    # My awesome comment
+    # And here the {$placeholder} is present
+        .aria-label = { $name } ({ $muted ->
+        [true] Muted{" "}
+        *[other] {""}
+    })
+```
+
+will be translated to:
+
+```ftl
+MY_KEY =
+    # My awesome comment
+    # And here the {$placeholder} os sintirp
+        .aria-label = { $name } ({ $muted ->
+        [true] Muted{" "}
+        *[other] {""}
+    })
+```
+
+This is because of the way the `@fluent/syntax` parser works at the current
+version. Fixing this would require either patching the parser behavior or adding
+extensive regex pre- and post-processing, both of which would increase
+complexity and reduce robustness. Given that this only affects comments, we
+prefer to wait for an upstream fix in a future version.
+
+**But keep in mind that whenever adding comments, it should be before the whole
+KEY = VALUE and not in between.**
+
 ## Context screenshots
 
 Context screenshots are, as their name suggest, screenshots that provide context
@@ -527,5 +723,5 @@ github action when a PR to main is merged.
 
 - [Fluent docs](https://github.com/projectfluent/fluent/wiki)
 - [I18n best practices](https://localization.blog/2022/05/16/i18n-best-practices-keep-it-together/)
-- [18n-services docs](../i18n-services/README.md)
-- [i18n for vue2 docs](../i18n-vue2/README.md)
+- [i18n-services docs (deprecated)](../../i18n-services/docs/README.md)
+- [i18n for vue2 docs (deprecated)](../../i18n-vue2/docs/README.md)

package/index.ts

@@ -1,3 +1,4 @@
+// Re-export everything from goblin-core
 export type {
   LocaleCode,
   NamespaceCode,
@@ -5,15 +6,27 @@ export type {
   LocaleManagerParams,
   SetLocaleParams,
   UseI18N,
-} from '@dialpad/i18n-services/locale-manager';
+  FluentFormat,
+  FluentFormatAttrs,
+  UniversalRef,
+  BundleSource,
+  Resource,
+  BuiltResource,
+  FTLModule,
+  HTTPBundleSourceParams,
+  RawBundleSourceParams,
+  StorageWrapper,
+} from '@dialpad/i18n-goblin-core';
 
-export type { BundleSource } from '@dialpad/i18n-services/bundle-source';
 export {
+  BaseLocaleManager,
   LocaleManager,
   useI18N,
+  findLocaleManager,
+  globalLocaleManagers,
   INJECTION_KEY_PREFIX,
-} from './src/locale-manager';
-export {
   HTTPBundleSource,
   RawBundleSource,
-} from '@dialpad/i18n-services/bundle-source';
+  createStorageWrapper,
+  MemoryStorageWrapper,
+} from '@dialpad/i18n-goblin-core';

package/package.json

@@ -1,31 +1,72 @@
 {
   "name": "@dialpad/i18n",
-  "version": "1.22.3",
+  "version": "1.24.0",
   "private": false,
-  "description": "Dialpad's internationalization library",
+  "description": "Internationalization library for Vue 3 apps using Mozilla's Fluent syntax, with locale management, translation bundle loading, and CLI tools for translation workflows",
+  "keywords": [
+    "i18n",
+    "internationalization",
+    "localization",
+    "fluent",
+    "vue",
+    "translation",
+    "locale"
+  ],
   "author": "Dialpad",
   "license": "UNLICENSED",
   "type": "module",
+  "files": [
+    "dist",
+    "bin",
+    "docs",
+    "index.ts"
+  ],
+  "scripts": {
+    "typecheck": "rushx types:check",
+    "typecheck:ci": "rushx typecheck",
+    "lint": "echo 'needs migration to use @dialpad/eslint-config'",
+    "lint:ci": "echo 'needs migration to use @dialpad/eslint-config'",
+    "format": "prettier ./ --write",
+    "format:ci": "prettier ./ --check",
+    "test": "vitest",
+    "test:ci": "echo 'no tests'",
+    "coverage": "vitest run --coverage --passWithNoTests",
+    "coverage:open": "rushx coverage && open coverage/index.html",
+    "build": "run-p build:*",
+    "build:main": "vite build --config vite.config.ts",
+    "build:types": "rushx types:build",
+    "types:build": "tsc",
+    "types:check": "tsc --noEmit"
+  },
   "dependencies": {
-    "@dialpad/i18n-services": "1.11.0"
+    "@dialpad/i18n-goblin-core": "1.0.2",
+    "@dialpad/i18n-goblin-services": "1.0.2"
   },
   "devDependencies": {
+    "@dialpad/eslint-config": "1.0.2",
     "@vitejs/plugin-vue": "~5.1.4",
     "npm-run-all": "4.1.5",
-    "prettier": "~2.8.8",
+    "prettier": "~3.3.3",
     "typescript": "~5.6.3",
     "vite": "~5.4.10",
     "vue": "~3.5.12",
-    "vue-tsc": "1.8.8",
-    "vitest": "~2.1.4",
     "eslint": "~9.13.0",
-    "@dialpad/eslint-config": "2.1.0"
+    "vue-tsc": "~3.1.1",
+    "vitest": "~2.1.4"
   },
   "exports": {
     "import": "./dist/i18n.js",
     "types": "./dist/types/index.d.ts",
     "require": "./dist/i18n.cjs"
   },
+  "bin": {
+    "translate-dialpadistan": "./bin/translate-dialpadistan.js",
+    "translation-screenshots-check": "./bin/translation-screenshots-check.js",
+    "upload-translation-service": "./bin/upload-translation-service.js",
+    "pull-translations": "./bin/pull-translations.js",
+    "force-pull-translations": "./bin/force-pull-translations.js",
+    "should-pull": "./bin/should-pull.js"
+  },
   "peerDependencies": {
     "vue": "^3.0.0"
   },
@@ -34,23 +75,6 @@
   },
   "repository": {
     "type": "git",
-    "url": "https://github.com/dialpad/web-clients.git"
-  },
-  "scripts": {
-    "typecheck": "rushx types:check",
-    "typecheck:ci": "rushx typecheck",
-    "lint": "echo 'needs migration to use @dialpad/eslint-config'",
-    "lint:ci": "echo 'needs migration to use @dialpad/eslint-config'",
-    "format": "prettier ./ --write",
-    "format:ci": "prettier ./ --check",
-    "test": "vitest",
-    "test:ci": "rushx test 2>&1",
-    "coverage": "vitest run --coverage --passWithNoTests",
-    "coverage:open": "rushx coverage && open coverage/index.html",
-    "build": "run-p build:*",
-    "build:main": "vite build --config vite.config.ts",
-    "build:types": "rushx types:build",
-    "types:build": "tsc",
-    "types:check": "tsc --noEmit"
+    "url": "https://github.com/dialpad/goblin-client-tools"
   }
-}
+}

package/.eslintignore

@@ -1 +0,0 @@
-dist

package/.eslintrc.cjs

@@ -1,12 +0,0 @@
-module.exports = {
-  extends: ['@dialpad'],
-  overrides: [
-    {
-      files: ['*.ts'],
-      parserOptions: {
-        project: ['./eslint-tsconfig.json'],
-        tsconfigRootDir: __dirname,
-      },
-    },
-  ],
-};