@seliseblocks/client 0.1.0-beta.0

package/dist/iam/iam-client.js

@@ -0,0 +1,230 @@
+export class BlocksIAMClient {
+    http;
+    constructor(http) {
+        this.http = http;
+    }
+    /**
+     * Current authenticated IAM account from `GET /iam/v4/iam/me`.
+     * Use this for app profile bootstrapping because it returns the Blocks user record,
+     * roles, permissions, and active organization context according to the access token.
+     */
+    me() {
+        return this.http.request("/iam/v4/iam/me");
+    }
+    /**
+     * Updates the current authenticated user's IAM profile through `POST /iam/v4/iam/me`.
+     * The backend resolves the user id from the token; callers must not send another user's id.
+     */
+    updateMe(request) {
+        return this.http.request("/iam/v4/iam/me", { body: request });
+    }
+    users = {
+        /**
+         * What: creates a user through `POST /iam/v4/iam/users/create`.
+         * Why: authorized admin UIs need to invite/provision users in the active tenant/organization.
+         * How: pass IAM's create-user payload; caller permissions determine whether the API accepts it.
+         */
+        create: (request) => this.http.request("/iam/v4/iam/users/create", { body: request }),
+        /**
+         * What: updates a user through `POST /iam/v4/iam/users/{id}`.
+         * Why: authorized admin UIs need to edit IAM profile fields.
+         * How: pass the user id in the route and IAM's update payload in the body.
+         */
+        update: (id, request) => this.http.request(`/iam/v4/iam/users/${encodeURIComponent(id)}`, { body: request }),
+        /**
+         * What: deactivates a user through `POST /iam/v4/iam/users/deactivate`.
+         * Why: admin UIs need to remove access without deleting the user record.
+         * How: pass IAM's deactivate payload for the target user.
+         */
+        deactivate: (request) => this.http.request("/iam/v4/iam/users/deactivate", { body: request }),
+        /**
+         * What: activates a user through `POST /iam/v4/iam/users/activate`.
+         * Why: admin UIs need to restore access for a previously inactive account.
+         * How: pass IAM's activate payload for the target user.
+         */
+        activate: (request) => this.http.request("/iam/v4/iam/users/activate", { body: request }),
+        /**
+         * What: queries users through `POST /iam/v4/iam/users`.
+         * Why: IAM uses a POST-read contract for paging/filtering user lists.
+         * How: pass `pageNo`, `pageSize`, search/filter fields, or the exact IAM list payload your UI needs.
+         */
+        list: (request = {}) => this.http.request("/iam/v4/iam/users", { body: request }),
+        /**
+         * What: reads one user through `GET /iam/v4/iam/users/{id}`.
+         * Why: user detail screens need one IAM user record, optionally for a specific organization context.
+         * How: pass the user id and optional `organizationId`.
+         */
+        get: (id, options = {}) => this.http.request(`/iam/v4/iam/users/${encodeURIComponent(id)}`, {
+            query: { organizationId: options.organizationId }
+        }),
+        /**
+         * What: updates user access through `POST /iam/v4/iam/users/access`.
+         * Why: admin UIs need to grant or change roles/permissions for a user.
+         * How: pass IAM's access payload; the active token and tenant header define allowed scope.
+         */
+        updateAccess: (request) => this.http.request("/iam/v4/iam/users/access", { body: request }),
+        /**
+         * What: revokes user access through `POST /iam/v4/iam/users/revoke-access`.
+         * Why: admin UIs need to remove roles/permissions or organization access.
+         * How: pass IAM's revoke-access payload.
+         */
+        revokeAccess: (request) => this.http.request("/iam/v4/iam/users/revoke-access", { body: request }),
+        /**
+         * What: checks email availability through `GET /iam/v4/iam/email/available`.
+         * Why: signup and invite forms can validate duplicate email state before submit.
+         * How: pass the email query fields IAM expects; this is public but still sends `x-blocks-key`.
+         */
+        emailAvailable: (query) => this.http.request("/iam/v4/iam/email/available", {
+            auth: false,
+            query
+        }),
+        /**
+         * What: checks whether a user exists through `GET /iam/v4/iam/users/exists`.
+         * Why: account and invite flows may need an existence check by email.
+         * How: pass the email string; the SDK sends it as the `email` query parameter.
+         */
+        exists: (email) => this.http.request("/iam/v4/iam/users/exists", { query: { email } })
+    };
+    permissions = {
+        /**
+         * What: creates a permission through `POST /iam/v4/iam/permissions/create`.
+         * Why: authorized admin tooling may manage custom IAM permission definitions.
+         * How: pass IAM's create-permission payload.
+         */
+        create: (request) => this.http.request("/iam/v4/iam/permissions/create", { body: request }),
+        /**
+         * What: updates a permission through `POST /iam/v4/iam/permissions/{id}`.
+         * Why: admin tooling may need to edit permission metadata.
+         * How: pass the permission id and IAM's update payload.
+         */
+        update: (id, request) => this.http.request(`/iam/v4/iam/permissions/${encodeURIComponent(id)}`, { body: request }),
+        /**
+         * What: queries permissions through `POST /iam/v4/iam/permissions`.
+         * Why: IAM uses a POST-read contract for permission paging/filtering.
+         * How: pass `pageNo`, `pageSize`, search/filter fields, or IAM's exact list payload.
+         */
+        list: (request = {}) => this.http.request("/iam/v4/iam/permissions", { body: request }),
+        /**
+         * What: groups permissions by severity through `GET /iam/v4/iam/permissions/by-severity`.
+         * Why: role/access UIs often display permissions grouped by risk or category.
+         * How: call after an authorized token is available.
+         */
+        bySeverity: () => this.http.request("/iam/v4/iam/permissions/by-severity"),
+        /**
+         * What: reads one permission through `GET /iam/v4/iam/permissions/{id}`.
+         * Why: admin detail/edit screens need one permission record.
+         * How: pass the permission id from IAM.
+         */
+        get: (id) => this.http.request(`/iam/v4/iam/permissions/${encodeURIComponent(id)}`)
+    };
+    roles = {
+        /**
+         * What: creates a role through `POST /iam/v4/iam/roles/create`.
+         * Why: admin UIs need to define permission bundles users can be assigned to.
+         * How: pass IAM's create-role payload.
+         */
+        create: (request) => this.http.request("/iam/v4/iam/roles/create", { body: request }),
+        /**
+         * What: updates a role through `POST /iam/v4/iam/roles/update`.
+         * Why: admin UIs need to edit role names, metadata, or other IAM-supported fields.
+         * How: pass IAM's role update payload.
+         */
+        update: (request) => this.http.request("/iam/v4/iam/roles/update", { body: request }),
+        /**
+         * What: queries roles through `POST /iam/v4/iam/roles`.
+         * Why: IAM uses a POST-read contract for role paging/filtering.
+         * How: pass `pageNo`, `pageSize`, search/filter fields, or IAM's exact list payload.
+         */
+        list: (request = {}) => this.http.request("/iam/v4/iam/roles", { body: request }),
+        /**
+         * What: reads one role through `GET /iam/v4/iam/roles/{id}`.
+         * Why: role detail/edit screens need one IAM role record.
+         * How: pass the role id from IAM.
+         */
+        get: (id) => this.http.request(`/iam/v4/iam/roles/${encodeURIComponent(id)}`),
+        /**
+         * What: assigns permissions to a role through `POST /iam/v4/iam/roles/assign-permissions`.
+         * Why: role editors need to attach or replace permission sets.
+         * How: pass IAM's assign-permissions payload.
+         */
+        assignPermissions: (request) => this.http.request("/iam/v4/iam/roles/assign-permissions", { body: request }),
+        /**
+         * What: lists assignable roles through `GET /iam/v4/iam/roles/assignable`.
+         * Why: user-access UIs should only show roles the current user can assign.
+         * How: call after an authorized token is available.
+         */
+        assignable: () => this.http.request("/iam/v4/iam/roles/assignable")
+    };
+    resources = {
+        /**
+         * What: lists resource groups through `GET /iam/v4/iam/resource-groups`.
+         * Why: permission screens need resource grouping metadata for navigation and display.
+         * How: call after an authorized token is available.
+         */
+        groups: () => this.http.request("/iam/v4/iam/resource-groups"),
+        /**
+         * What: lists feature/resource flags through `GET /iam/v4/iam/resource/features`.
+         * Why: frontends use this to feature-gate UI based on current roles and permissions.
+         * How: pass optional query fields supported by IAM; the active token defines the user context.
+         */
+        features: (query = {}) => this.http.request("/iam/v4/iam/resource/features", { query })
+    };
+    organizations = {
+        /**
+         * What: creates an organization through `POST /iam/v4/iam/organizations/create`.
+         * Why: authorized admin UIs may need tenant organization management.
+         * How: pass IAM's create-organization payload.
+         */
+        create: (request) => this.http.request("/iam/v4/iam/organizations/create", { body: request }),
+        /**
+         * What: updates an organization through `POST /iam/v4/iam/organizations/{id}`.
+         * Why: organization settings screens need to edit metadata/config.
+         * How: pass the organization id and IAM's update payload.
+         */
+        update: (id, request) => this.http.request(`/iam/v4/iam/organizations/${encodeURIComponent(id)}`, { body: request }),
+        /**
+         * What: lists organizations through `GET /iam/v4/iam/organizations`.
+         * Why: admin UIs need organization browsing and selection.
+         * How: pass IAM-supported query fields such as paging/search options.
+         */
+        list: (query = {}) => this.http.request("/iam/v4/iam/organizations", { query }),
+        /**
+         * What: reads one organization through `GET /iam/v4/iam/organizations/{id}`.
+         * Why: organization detail screens need one organization record.
+         * How: pass the organization id from IAM.
+         */
+        get: (id) => this.http.request(`/iam/v4/iam/organizations/${encodeURIComponent(id)}`),
+        /**
+         * What: lists current-user organizations through `GET /iam/v4/iam/organizations/my`.
+         * Why: apps need available organizations for org switchers and context selectors.
+         * How: call with the current user's access token.
+         */
+        my: () => this.http.request("/iam/v4/iam/organizations/my"),
+        /**
+         * What: reads organization configuration through `GET /iam/v4/iam/organizations/config`.
+         * Why: settings screens need the active organization's current configuration.
+         * How: call with an authorized token in the desired organization context.
+         */
+        getConfig: () => this.http.request("/iam/v4/iam/organizations/config"),
+        /**
+         * What: saves organization configuration through `POST /iam/v4/iam/organizations/config`.
+         * Why: settings screens need to persist organization-level behavior.
+         * How: pass IAM's organization config payload.
+         */
+        saveConfig: (request) => this.http.request("/iam/v4/iam/organizations/config", { body: request })
+    };
+    signupSettings = {
+        /**
+         * What: reads signup settings through `GET /iam/v4/iam/signup-settings`.
+         * Why: public signup screens need tenant policy before a user is authenticated.
+         * How: call without an access token; the SDK still sends `x-blocks-key`.
+         */
+        get: () => this.http.request("/iam/v4/iam/signup-settings", { auth: false }),
+        /**
+         * What: saves signup settings through `POST /iam/v4/iam/signup-settings`.
+         * Why: admin/settings screens need to configure signup policy.
+         * How: pass IAM's signup-settings payload with an authorized token.
+         */
+        save: (request) => this.http.request("/iam/v4/iam/signup-settings", { body: request })
+    };
+}

package/dist/iam/types.d.ts

@@ -0,0 +1,56 @@
+export type BlocksBaseResponse = Record<string, unknown> & {
+    errors?: unknown;
+    isSuccess?: boolean;
+    message?: string;
+};
+export type BlocksQueryResponse<T = unknown> = BlocksBaseResponse & {
+    data?: T;
+};
+export type BlocksQueryListResponse<T = unknown> = BlocksBaseResponse & {
+    data?: T[];
+    pageNo?: number;
+    pageSize?: number;
+    totalCount?: number;
+};
+export type BlocksUser = Record<string, unknown> & {
+    active?: boolean;
+    email?: string;
+    firstName?: string;
+    itemId?: string;
+    language?: string;
+    lastName?: string;
+    permissions?: string[];
+    roles?: string[];
+    status?: number;
+};
+export type BlocksPermission = Record<string, unknown> & {
+    itemId?: string;
+    resource?: string;
+    roles?: string[];
+};
+export type BlocksRole = Record<string, unknown> & {
+    itemId?: string;
+    name?: string;
+    slug?: string;
+};
+export type BlocksOrganization = Record<string, unknown> & {
+    itemId?: string;
+    name?: string;
+};
+export type BlocksIamListRequest<TFilter = Record<string, unknown>> = Record<string, unknown> & {
+    filter?: TFilter;
+    pageNo?: number;
+    pageNumber?: number;
+    pageSize?: number;
+    search?: string;
+};
+export type BlocksMeResponse = BlocksQueryResponse<BlocksUser>;
+export type BlocksGetUserResponse = BlocksQueryResponse<BlocksUser>;
+export type BlocksGetUsersResponse = BlocksQueryListResponse<BlocksUser>;
+export type BlocksGetPermissionResponse = BlocksQueryResponse<BlocksPermission>;
+export type BlocksGetPermissionsResponse = BlocksQueryListResponse<BlocksPermission>;
+export type BlocksGetRoleResponse = BlocksQueryResponse<BlocksRole>;
+export type BlocksGetRolesResponse = BlocksQueryListResponse<BlocksRole>;
+export type BlocksGetOrganizationResponse = BlocksQueryResponse<BlocksOrganization>;
+export type BlocksGetOrganizationsResponse = BlocksQueryListResponse<BlocksOrganization>;
+export type BlocksGetMyOrganizationsResponse = BlocksQueryResponse<BlocksOrganization[]>;

package/dist/iam/types.js

@@ -0,0 +1 @@
+export {};

package/dist/index.d.ts

@@ -0,0 +1,12 @@
+export { createBlocksClient } from "./client.js";
+export { BlocksAuthenticationClient } from "./auth/auth-client.js";
+export { BlocksDataClient } from "./data/data-client.js";
+export type { BlocksClient, BlocksClientConfig, BlocksOidcConfig } from "./client.js";
+export { BlocksApiError } from "./http/errors.js";
+export { BlocksIAMClient } from "./iam/iam-client.js";
+export { BlocksLocalizationClient } from "./localization/localization-client.js";
+export type { BlocksAuthPassThroughResponse, BlocksAuthResponse, BlocksClientCredentialsRequest, BlocksAuthLoginRequest, BlocksIdpCallbackRequest, BlocksIdpInitiateRequest, BlocksIdpInitiateResponse, BlocksLoginOption, BlocksLogoutRequest, BlocksOidcRefreshRequest, BlocksOidcUserInfo, BlocksRefreshRequest, BlocksSocialLoginRequest, BlocksSwitchOrganizationRequest } from "./auth/auth-client.js";
+export type { BlocksRequestOptions } from "./types.js";
+export type { BlocksBaseResponse, BlocksGetMyOrganizationsResponse, BlocksGetOrganizationResponse, BlocksGetOrganizationsResponse, BlocksGetPermissionResponse, BlocksGetPermissionsResponse, BlocksGetRoleResponse, BlocksGetRolesResponse, BlocksGetUserResponse, BlocksGetUsersResponse, BlocksIamListRequest, BlocksMeResponse, BlocksOrganization, BlocksPermission, BlocksQueryListResponse, BlocksQueryResponse, BlocksRole, BlocksUser } from "./iam/types.js";
+export type { BlocksDataCollection, BlocksDataListOptions, BlocksDmsCreateFolderRequest, BlocksDmsListRequest, BlocksDmsMetaDataValue, BlocksDmsUploadItem, BlocksDmsUploadRequest, BlocksFileDeleteRequest, BlocksFileGetOptions, BlocksFileInfoListRequest, BlocksFileListRequest, BlocksFileUpdateAdditionalInfoRequest, BlocksFileUploadRequest, BlocksFolderDeleteRequest, BlocksGraphqlRequest, BlocksLocalStorageUploadRequest, BlocksPagedResult, BlocksRegexGenerateRequest, BlocksSchemaFieldValidationOptions, BlocksSchemaListOptions, BlocksSchemaValidationListOptions, BlocksUploadToUrlRequest } from "./data/types.js";
+export type { BlocksLocalizationDictionary, BlocksLocalizationKey, BlocksLocalizationKeysByNamesRequest, BlocksLocalizationKeysByNamesResponse, BlocksLocalizationLanguage, BlocksLocalizationModule, BlocksLocalizationTranslationOptions } from "./localization/types.js";

package/dist/index.js

@@ -0,0 +1,6 @@
+export { createBlocksClient } from "./client.js";
+export { BlocksAuthenticationClient } from "./auth/auth-client.js";
+export { BlocksDataClient } from "./data/data-client.js";
+export { BlocksApiError } from "./http/errors.js";
+export { BlocksIAMClient } from "./iam/iam-client.js";
+export { BlocksLocalizationClient } from "./localization/localization-client.js";

package/dist/localization/localization-client.d.ts

@@ -0,0 +1,71 @@
+import { BlocksHttpClient } from "../http/http-client.js";
+import { BlocksLocalizationDictionary, BlocksLocalizationKeysByNamesRequest, BlocksLocalizationKeysByNamesResponse, BlocksLocalizationLanguage, BlocksLocalizationModule } from "./types.js";
+export declare class BlocksLocalizationClient {
+    private readonly http;
+    private readonly dictionaries;
+    private activeLanguage;
+    constructor(http: BlocksHttpClient);
+    /**
+     * What: lists available languages through `GET /localization/v4/Language/Gets`.
+     * Why: apps need tenant-supported cultures for language pickers and startup locale selection.
+     * How: call without an access token; the SDK still sends `x-blocks-key`.
+     */
+    languages(): Promise<BlocksLocalizationLanguage[]>;
+    /**
+     * What: lists available localization modules through `GET /localization/v4/Module/Gets`.
+     * Why: apps can discover which translation bundles exist for the tenant.
+     * How: call without an access token; the SDK still sends `x-blocks-key`.
+     */
+    modules(): Promise<BlocksLocalizationModule[]>;
+    /**
+     * What: loads one module dictionary through `GET /localization/v4/Key/GetUilmFile`.
+     * Why: framework-neutral apps need raw translation dictionaries without adopting a specific i18n library.
+     * How: pass `moduleName` and `language`; the SDK normalizes string values and caches the dictionary in this client instance.
+     */
+    translations(moduleName: string, language: string): Promise<BlocksLocalizationDictionary>;
+    /**
+     * What: lists languages resolved for the active Blocks tenant through `GET /localization/v4/Language/GetLanguagesForCurrentTenant`.
+     * Why: multi-tenant apps should show the languages actually enabled for the tenant behind the current `x-blocks-key`.
+     * How: call during app startup or settings screen load; the SDK sends `x-blocks-key` and the caller access token when configured.
+     */
+    languagesForCurrentTenant(): Promise<BlocksLocalizationLanguage[]>;
+    /**
+     * What: lists localization modules resolved for the active Blocks tenant through `GET /localization/v4/Module/GetModulesForCurrentTenant`.
+     * Why: apps can discover tenant-scoped bundles such as `common`, `dashboard`, or feature modules before loading translations.
+     * How: call with the configured client; the tenant is selected by `x-blocks-key`, not by a `ProjectKey` query/body value.
+     */
+    modulesForCurrentTenant(): Promise<BlocksLocalizationModule[]>;
+    /**
+     * What: loads the authorized cloud UILM dictionary through `GET /localization/v4/Key/GetCloudUilmFile`.
+     * Why: signed-in app surfaces can load protected tenant dictionaries while keeping session/token ownership in the caller app.
+     * How: pass `moduleName` and `language`; the SDK sends the caller access token when configured, normalizes string values, and caches the result for `t()`.
+     */
+    cloudTranslations(moduleName: string, language: string): Promise<BlocksLocalizationDictionary>;
+    /**
+     * What: retrieves exact localization key records through `POST /localization/v4/Key/GetsByKeyNames`.
+     * Why: apps sometimes need key metadata or selected translations without downloading a whole module dictionary.
+     * How: pass `keyNames` and optional `moduleId`; the SDK posts the body as-is except it removes any accidental `ProjectKey`/`projectKey`.
+     */
+    keysByNames(request: BlocksLocalizationKeysByNamesRequest): Promise<BlocksLocalizationKeysByNamesResponse>;
+    /**
+     * What: loads multiple module dictionaries and merges them.
+     * Why: most apps need several translation modules during startup.
+     * How: pass a language and module list; later modules overwrite earlier keys if the same key appears twice.
+     */
+    load(language: string, modules: string[]): Promise<BlocksLocalizationDictionary>;
+    /**
+     * What: loads multiple authorized cloud UILM dictionaries and merges them.
+     * Why: signed-in runtime areas can hydrate all protected translation modules needed for a screen in one app-level call.
+     * How: pass a language and module list; later modules overwrite earlier keys if the same key appears twice.
+     */
+    loadCloud(language: string, modules: string[]): Promise<BlocksLocalizationDictionary>;
+    /**
+     * What: resolves a translated string from dictionaries already loaded by `translations()` or `load()`.
+     * Why: simple apps can read labels without adding a framework-specific localization package.
+     * How: pass a key, optional fallback, and optional `language`/`moduleName`; missing keys return fallback or the key.
+     */
+    t(key: string, fallback?: string, options?: {
+        language?: string;
+        moduleName?: string;
+    }): string;
+}

package/dist/localization/localization-client.js

@@ -0,0 +1,148 @@
+const LOCALIZATION_API = "/localization/v4";
+export class BlocksLocalizationClient {
+    http;
+    dictionaries = new Map();
+    activeLanguage = "";
+    constructor(http) {
+        this.http = http;
+    }
+    /**
+     * What: lists available languages through `GET /localization/v4/Language/Gets`.
+     * Why: apps need tenant-supported cultures for language pickers and startup locale selection.
+     * How: call without an access token; the SDK still sends `x-blocks-key`.
+     */
+    languages() {
+        return this.http.request(`${LOCALIZATION_API}/Language/Gets`, {
+            auth: false
+        });
+    }
+    /**
+     * What: lists available localization modules through `GET /localization/v4/Module/Gets`.
+     * Why: apps can discover which translation bundles exist for the tenant.
+     * How: call without an access token; the SDK still sends `x-blocks-key`.
+     */
+    modules() {
+        return this.http.request(`${LOCALIZATION_API}/Module/Gets`, {
+            auth: false
+        });
+    }
+    /**
+     * What: loads one module dictionary through `GET /localization/v4/Key/GetUilmFile`.
+     * Why: framework-neutral apps need raw translation dictionaries without adopting a specific i18n library.
+     * How: pass `moduleName` and `language`; the SDK normalizes string values and caches the dictionary in this client instance.
+     */
+    async translations(moduleName, language) {
+        const result = await this.http.request(`${LOCALIZATION_API}/Key/GetUilmFile`, {
+            auth: false,
+            query: { Language: language, ModuleName: moduleName }
+        });
+        const dictionary = normalizeDictionary(result);
+        this.dictionaries.set(cacheKey(language, moduleName), dictionary);
+        this.activeLanguage = language;
+        return dictionary;
+    }
+    /**
+     * What: lists languages resolved for the active Blocks tenant through `GET /localization/v4/Language/GetLanguagesForCurrentTenant`.
+     * Why: multi-tenant apps should show the languages actually enabled for the tenant behind the current `x-blocks-key`.
+     * How: call during app startup or settings screen load; the SDK sends `x-blocks-key` and the caller access token when configured.
+     */
+    languagesForCurrentTenant() {
+        return this.http.request(`${LOCALIZATION_API}/Language/GetLanguagesForCurrentTenant`);
+    }
+    /**
+     * What: lists localization modules resolved for the active Blocks tenant through `GET /localization/v4/Module/GetModulesForCurrentTenant`.
+     * Why: apps can discover tenant-scoped bundles such as `common`, `dashboard`, or feature modules before loading translations.
+     * How: call with the configured client; the tenant is selected by `x-blocks-key`, not by a `ProjectKey` query/body value.
+     */
+    modulesForCurrentTenant() {
+        return this.http.request(`${LOCALIZATION_API}/Module/GetModulesForCurrentTenant`);
+    }
+    /**
+     * What: loads the authorized cloud UILM dictionary through `GET /localization/v4/Key/GetCloudUilmFile`.
+     * Why: signed-in app surfaces can load protected tenant dictionaries while keeping session/token ownership in the caller app.
+     * How: pass `moduleName` and `language`; the SDK sends the caller access token when configured, normalizes string values, and caches the result for `t()`.
+     */
+    async cloudTranslations(moduleName, language) {
+        const result = await this.http.request(`${LOCALIZATION_API}/Key/GetCloudUilmFile`, {
+            query: { Language: language, ModuleName: moduleName }
+        });
+        const dictionary = normalizeDictionary(result);
+        this.dictionaries.set(cacheKey(language, moduleName), dictionary);
+        this.activeLanguage = language;
+        return dictionary;
+    }
+    /**
+     * What: retrieves exact localization key records through `POST /localization/v4/Key/GetsByKeyNames`.
+     * Why: apps sometimes need key metadata or selected translations without downloading a whole module dictionary.
+     * How: pass `keyNames` and optional `moduleId`; the SDK posts the body as-is except it removes any accidental `ProjectKey`/`projectKey`.
+     */
+    keysByNames(request) {
+        return this.http.request(`${LOCALIZATION_API}/Key/GetsByKeyNames`, {
+            body: withoutProjectKey(request),
+            method: "POST"
+        });
+    }
+    /**
+     * What: loads multiple module dictionaries and merges them.
+     * Why: most apps need several translation modules during startup.
+     * How: pass a language and module list; later modules overwrite earlier keys if the same key appears twice.
+     */
+    async load(language, modules) {
+        const dictionaries = await Promise.all(modules.map((moduleName) => this.translations(moduleName, language)));
+        return Object.assign({}, ...dictionaries);
+    }
+    /**
+     * What: loads multiple authorized cloud UILM dictionaries and merges them.
+     * Why: signed-in runtime areas can hydrate all protected translation modules needed for a screen in one app-level call.
+     * How: pass a language and module list; later modules overwrite earlier keys if the same key appears twice.
+     */
+    async loadCloud(language, modules) {
+        const dictionaries = await Promise.all(modules.map((moduleName) => this.cloudTranslations(moduleName, language)));
+        return Object.assign({}, ...dictionaries);
+    }
+    /**
+     * What: resolves a translated string from dictionaries already loaded by `translations()` or `load()`.
+     * Why: simple apps can read labels without adding a framework-specific localization package.
+     * How: pass a key, optional fallback, and optional `language`/`moduleName`; missing keys return fallback or the key.
+     */
+    t(key, fallback, options = {}) {
+        const language = options.language ?? this.activeLanguage;
+        if (options.moduleName) {
+            return this.dictionaries.get(cacheKey(language, options.moduleName))?.[key] ?? fallback ?? key;
+        }
+        for (const [dictionaryKey, dictionary] of this.dictionaries) {
+            if (language && !dictionaryKey.startsWith(`${language}:`))
+                continue;
+            const value = dictionary[key];
+            if (value)
+                return value;
+        }
+        return fallback ?? key;
+    }
+}
+function normalizeDictionary(value) {
+    if (typeof value === "object" && value) {
+        const record = value;
+        if (typeof record.data === "object" && record.data)
+            return stringifyValues(record.data);
+        return stringifyValues(record);
+    }
+    return {};
+}
+function stringifyValues(record) {
+    const result = {};
+    for (const [key, value] of Object.entries(record)) {
+        if (typeof value === "string")
+            result[key] = value;
+    }
+    return result;
+}
+function cacheKey(language, moduleName) {
+    return `${language}:${moduleName}`;
+}
+function withoutProjectKey(value) {
+    const clone = { ...value };
+    delete clone.ProjectKey;
+    delete clone.projectKey;
+    return clone;
+}

package/dist/localization/types.d.ts

@@ -0,0 +1,35 @@
+export type BlocksLocalizationLanguage = Record<string, unknown> & {
+    itemId?: string;
+    code?: string;
+    culture?: string;
+    displayName?: string;
+    isDefault?: boolean;
+    languageCode?: string;
+    languageName?: string;
+    name?: string;
+};
+export type BlocksLocalizationModule = Record<string, unknown> & {
+    itemId?: string;
+    moduleName?: string;
+    name?: string;
+};
+export type BlocksLocalizationDictionary = Record<string, string>;
+export type BlocksLocalizationTranslationOptions = {
+    language: string;
+    moduleName: string;
+};
+export type BlocksLocalizationKey = Record<string, unknown> & {
+    itemId?: string;
+    keyName?: string;
+    moduleId?: string;
+    moduleName?: string;
+    values?: Record<string, unknown>;
+};
+export type BlocksLocalizationKeysByNamesRequest = {
+    keyNames: string[];
+    moduleId?: string;
+};
+export type BlocksLocalizationKeysByNamesResponse = Record<string, unknown> & {
+    keys?: BlocksLocalizationKey[];
+    errorMessage?: string;
+};

package/dist/localization/types.js

@@ -0,0 +1 @@
+export {};

package/dist/types.d.ts

@@ -0,0 +1,13 @@
+export type BlocksRequestOptions = {
+    accessToken?: string;
+    auth?: boolean;
+    body?: unknown;
+    headers?: HeadersInit;
+    method?: string;
+    query?: Record<string, boolean | number | string | undefined>;
+};
+export type BlocksExternalRequestOptions = {
+    body?: BodyInit | null;
+    headers?: HeadersInit;
+    method?: string;
+};

package/dist/types.js

@@ -0,0 +1 @@
+export {};

package/package.json

@@ -0,0 +1,48 @@
+{
+  "name": "@seliseblocks/client",
+  "version": "0.1.0-beta.0",
+  "description": "Framework-neutral TypeScript client SDK for SELISE Blocks frontend applications.",
+  "license": "MIT",
+  "type": "module",
+  "keywords": [
+    "selise",
+    "blocks",
+    "sdk",
+    "typescript",
+    "frontend"
+  ],
+  "main": "./dist/index.js",
+  "types": "./dist/index.d.ts",
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "import": "./dist/index.js"
+    },
+    "./package.json": "./package.json"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "sideEffects": false,
+  "files": [
+    "dist",
+    "README.md",
+    "AI_USAGE_GUIDE.md",
+    "LICENSE"
+  ],
+  "scripts": {
+    "clean": "node -e \"require('node:fs').rmSync('dist',{recursive:true,force:true})\"",
+    "build": "npm run clean && tsc -p tsconfig.json",
+    "lint": "tsc -p tsconfig.json --noEmit",
+    "test": "npm run build && node --test test/*.test.mjs",
+    "prepack": "npm run build",
+    "prepublishOnly": "npm test"
+  },
+  "engines": {
+    "node": ">=20"
+  },
+  "devDependencies": {
+    "@types/node": "^22.0.0",
+    "typescript": "^5.5.0"
+  }
+}