{
  "name": "@tygaria/tygazen",
  "version": "0.6.0",
  "description": "The one game-integration surface for the TYGA game center (tygazen.com) on the web: native signup, the pixel face builder, and clip-moment telemetry. One tygazen, one face, every game.",
  "repository": {
    "type": "git",
    "url": "git+https://github.com/jyswee/tygazen-js-sdk.git"
  },
  "homepage": "https://github.com/jyswee/tygazen-js-sdk#readme",
  "bugs": {
    "url": "https://github.com/jyswee/tygazen-js-sdk/issues"
  },
  "type": "module",
  "main": "./dist/index.js",
  "exports": {
    ".": {
      "types": "./dist/tygazen.d.ts",
      "default": "./dist/index.js"
    },
    "./package.json": "./package.json",
    "./pixel-options": "./dist/avatar/pixel-options.cjs",
    "./pixel-editor": "./dist/avatar/pixel-editor.js",
    "./browser": "./dist/tygazen.browser.js"
  },
  "// files": "dist/progress/ IS in this list, and 0.3.0 learning why cost two partners a workaround. Withholding TygaZen.Progress because dist/tygazen.d.ts does not declare it was a reasonable call applied at the wrong layer: dist/index.js STATICALLY re-exports ./progress/index.js, so leaving the folder out of the tarball did not hide a surface, it made every entry that reaches it throw ERR_MODULE_NOT_FOUND (BUG-2026-1030-0220). An allowlist is a hand-kept list, which is the exact shape scripts/build.cjs stopped using after src/pool/roster.js was missed; the answer is not a better list but scripts/verify-pack.cjs, which imports the TARBALL. Progress is now declared in the .d.ts too, so the types describe what ships.",
  "files": [
    "dist/avatar/",
    "dist/clips/",
    "dist/identity/",
    "dist/pool/",
    "dist/progress/",
    "dist/news/",
    "dist/care/",
    "dist/rooms/",
    "dist/graph/",
    "dist/index.js",
    "dist/tygazen.browser.js",
    "dist/tygazen.d.ts",
    "README.md",
    "CHANGELOG.md",
    "COPYRIGHT",
    "LICENSE.md",
    "Third Party Notices.md"
  ],
  "license": "SEE LICENSE IN COPYRIGHT",
  "author": {
    "name": "Tyga.Cloud Ltd",
    "url": "https://tygazen.com"
  },
  "keywords": [
    "tyga",
    "tygazen",
    "game center",
    "avatar",
    "signup",
    "clips",
    "telemetry"
  ],
  "peerDependencies": {
    "@dicebear/core": "9.4.3",
    "@dicebear/pixel-art": "9.4.3"
  },
  "// sideEffects": "NOT false. avatar/options.js exists FOR its side effect \u2014 it publishes the config->options mapping on globalThis.PixelOptions, which pixel-editor.js reads at module scope. With sideEffects:false a bundler is free to drop `import './avatar/options.js'` entirely, and esbuild says so out loud: \"Ignoring this import because dist/avatar/options.js was marked as having no side effects\". Every bundled consumer therefore had no global and a dead editor. Naming the one file that has side effects keeps the tree-shaking everywhere else.",
  "sideEffects": [
    "./src/avatar/options.js",
    "./dist/avatar/options.js"
  ],
  "scripts": {
    "build": "node scripts/build.cjs && npm run build:browser && npm run build:types",
    "verify": "node scripts/verify-pack.cjs",
    "build:browser": "node scripts/build-browser.cjs",
    "build:types": "cp src/index.d.ts dist/tygazen.d.ts",
    "clean": "rm -rf dist"
  },
  "devDependencies": {
    "@dicebear/core": "9.4.3",
    "@dicebear/pixel-art": "9.4.3",
    "esbuild": "0.25.0"
  },
  "types": "./dist/tygazen.d.ts"
}
