@lokalise/api-contracts/package.json

Key idea behind API contracts: backend owns entire definition for the route, including its path, HTTP method used and response structure expectations, and exposes it as a part of its API schemas. Then frontend consumes that definition instead of forming f

{
    "name": "@lokalise/api-contracts",
    "version": "5.0.0",
    "files": ["dist"],
    "license": "Apache-2.0",
    "type": "module",
    "main": "./dist/apiContracts.js",
    "enableTransparentWorkspaces": "false",
    "homepage": "https://github.com/lokalise/shared-ts-libs",
    "repository": {
        "type": "git",
        "url": "git://github.com/lokalise/shared-ts-libs.git"
    },
    "exports": {
        ".": "./dist/apiContracts.js",
        "./package.json": "./package.json"
    },
    "private": false,
    "publishConfig": {
        "access": "public"
    },
    "keywords": [
        "api",
        "contracts",
        "contract",
        "frontend",
        "backend",
        "single",
        "source",
        "truth"
    ],
    "scripts": {
        "build": "rimraf dist && tsc --project tsconfig.build.json",
        "lint": "biome check . && tsc",
        "lint:fix": "biome check --write",
        "test": "vitest run",
        "test:ci": "vitest run --coverage",
        "prepublishOnly": "npm run build",
        "package-version": "echo $npm_package_version",
        "postversion": "biome check --write package.json"
    },
    "peerDependencies": {
        "zod": ">=3.25.56"
    },
    "devDependencies": {
        "@biomejs/biome": "^1.9.4",
        "@lokalise/biome-config": "^2.0.0",
        "@lokalise/tsconfig": "^1.3.0",
        "@vitest/coverage-v8": "^3.2.2",
        "rimraf": "^6.0.1",
        "typescript": "5.8.3",
        "vitest": "^3.2.2"
    },
    "dependencies": {}
}