{"_id":"@blobatar/vue","_rev":"7-203c4d3e3ffa6693dd77d5951415a167","name":"@blobatar/vue","dist-tags":{"latest":"2.7.0"},"versions":{"2.2.0":{"name":"@blobatar/vue","version":"2.2.0","keywords":["blobatar","avatar","identicon","vue","svg","deterministic"],"author":{"name":"Alain"},"license":"MIT","_id":"@blobatar/vue@2.2.0","maintainers":[{"name":"alain00","email":"alain00.alvarez@gmail.com"}],"homepage":"https://github.com/Alain00/blobatar#readme","bugs":{"url":"https://github.com/Alain00/blobatar/issues"},"dist":{"shasum":"c150f7f0c1e020c2b78cb8f50af4276c590e94bb","tarball":"https://registry.npmjs.org/@blobatar/vue/-/vue-2.2.0.tgz","fileCount":8,"integrity":"sha512-tTFbi0vZs8f01XVn36niI/A0Db2KdkOMC3d1s6ie3eVQLHgGK/qW7N6brjC+iFZ16k4BRiHVhdyYXOexnwbBzw==","signatures":[{"sig":"MEUCIQCPx4rq51IFZVfsuiBgDz/Q38zBNx9t3YTh80u+ekul+AIgYvrbfH99GjXyVVR78Kt/vDWvXkc0EzdycL0GFpP2zNs=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"unpackedSize":10955},"main":"./dist/index.js","type":"module","types":"./dist/index.d.ts","//check":"No `bun run build` here. The build is a turbo task that `check` depends on, so it runs once for the whole workspace before any check reads a `dist` — a check that rebuilt its own package would delete `dist` out from under a concurrent check in another one.","exports":{".":{"types":"./dist/index.d.ts","default":"./dist/index.js"},"./package.json":"./package.json"},"gitHead":"a45df3cbd0fa4c8a17216ae466b4d2ffd8120db8","scripts":{"build":"bun scripts/build.ts","check":"bun run typecheck","typecheck":"tsc -p tsconfig.json --noEmit"},"_npmUser":{"name":"alain00","email":"alain00.alvarez@gmail.com"},"repository":{"url":"git+https://github.com/Alain00/blobatar.git","type":"git","directory":"packages/vue"},"_npmVersion":"10.9.3","description":"Vue 3 adapter for blobatar — deterministic geometric avatars.","directories":{},"sideEffects":["*.css"],"_nodeVersion":"22.19.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"vue":"^3.5.0","blobatar":"workspace:*"},"peerDependencies":{"vue":">=3","blobatar":"2.x"},"//peerDependencies":"`blobatar` is pinned to an exact major, not `^3`. Every package in this set publishes the same version (`.changeset/config.json`), and npm does not enforce that at install time — without the exact range, `@blobatar/react@4` resolves happily alongside `blobatar@3` and renders a different generation's faces from a package the consumer believes is current. Under ADR-0008 the major names the generation, so a mixed pair is not a version skew, it is the wrong picture. `packages/harness` asserts this range rather than trusting it, because release tooling rewrites workspace ranges and would quietly turn it into a caret.","_npmOperationalInternal":{"tmp":"tmp/vue_2.2.0_1787179218325_0.06892292543298928","host":"s3://npm-registry-packages-npm-production"}},"2.3.0":{"name":"@blobatar/vue","version":"2.3.0","keywords":["blobatar","avatar","identicon","vue","svg","deterministic"],"author":{"name":"Alain"},"license":"MIT","_id":"@blobatar/vue@2.3.0","maintainers":[{"name":"alain00","email":"alain00.alvarez@gmail.com"}],"homepage":"https://github.com/Alain00/blobatar#readme","bugs":{"url":"https://github.com/Alain00/blobatar/issues"},"dist":{"shasum":"9ecf5709bee677cb4baadcbb243f910ef3607891","tarball":"https://registry.npmjs.org/@blobatar/vue/-/vue-2.3.0.tgz","fileCount":8,"integrity":"sha512-WsDFRzVCOCai48FzH9EzPluVFzkfAqtlmOy+K2i2itlzM4xf83KOf048pxYHpj70f/9n3YWKsg5CS+oi0INloQ==","signatures":[{"sig":"MEYCIQCteBKWxZ5//wyLbDvq+PnWnUzOyL1B84a2xAXiuH11ggIhAIqaDcH+AsJ3klTnYh6wvQAiFaA522JDnRCF05LXVofS","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@blobatar%2fvue@2.3.0","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":11761},"main":"./dist/index.js","type":"module","types":"./dist/index.d.ts","//check":"No `bun run build` here. The build is a turbo task that `check` depends on, so it runs once for the whole workspace before any check reads a `dist` — a check that rebuilt its own package would delete `dist` out from under a concurrent check in another one.","exports":{".":{"types":"./dist/index.d.ts","default":"./dist/index.js"},"./package.json":"./package.json"},"gitHead":"bdabadddac79b407d61d383dee860c8a97e5719d","scripts":{"build":"bun scripts/build.ts","check":"bun run typecheck","prepack":"bun run build","//prepack":"This does not contradict `//check` below, and the difference is who owns the build. Under `check`, turbo owns it: the `build` task runs once for the whole workspace before any check reads a `dist`, so a check that rebuilt its own package would delete one out from under a concurrent check in another. Under `npm pack` and `npm publish` there is no turbo and no ordering — npm runs one lifecycle in one package — so without this the tarball is whatever `dist` happened to be on disk, which for a package built from a peer dependency can be stale, from another branch, or absent entirely. Core carried this from the start; the adapters were published by hand once without it, and only a manual `npm pack --dry-run` caught that the contents were right.","typecheck":"tsc -p tsconfig.json --noEmit"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:e9c45dab-7c9d-4585-b967-3b35266938d5"}},"repository":{"url":"git+https://github.com/Alain00/blobatar.git","type":"git","directory":"packages/vue"},"_npmVersion":"12.0.2","description":"Vue 3 adapter for blobatar — deterministic geometric avatars.","directories":{},"sideEffects":["*.css"],"_nodeVersion":"22.23.2","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"vue":"^3.5.0","blobatar":"workspace:*"},"peerDependencies":{"vue":">=3","blobatar":"2.x"},"//peerDependencies":"`blobatar` is pinned to an exact major, not `^3`. Every package in this set publishes the same version (`.changeset/config.json`), and npm does not enforce that at install time — without the exact range, `@blobatar/react@4` resolves happily alongside `blobatar@3` and renders a different generation's faces from a package the consumer believes is current. Under ADR-0008 the major names the generation, so a mixed pair is not a version skew, it is the wrong picture. `packages/harness` asserts this range rather than trusting it, because release tooling rewrites workspace ranges and would quietly turn it into a caret.","_npmOperationalInternal":{"tmp":"tmp/vue_2.3.0_1787232132810_0.7520261099203411","host":"s3://npm-registry-packages-npm-production"}},"2.3.1":{"name":"@blobatar/vue","version":"2.3.1","keywords":["blobatar","avatar","identicon","vue","svg","deterministic"],"author":{"name":"Alain"},"license":"MIT","_id":"@blobatar/vue@2.3.1","maintainers":[{"name":"alain00","email":"alain00.alvarez@gmail.com"}],"homepage":"https://github.com/Alain00/blobatar#readme","bugs":{"url":"https://github.com/Alain00/blobatar/issues"},"dist":{"shasum":"b520f110a1e1b269d394d6ac812b885e4311a73c","tarball":"https://registry.npmjs.org/@blobatar/vue/-/vue-2.3.1.tgz","fileCount":8,"integrity":"sha512-mJKES/l0vHfSSBfyd2BHPc113aHe+495L90aBFpce6AUzkMZx0ExXpZBw+7WtxutNxBC/va+2Y401uX75OzsVA==","signatures":[{"sig":"MEUCIEznmlPsAEbRBEptRETHTI11h85i/ecOq28/9z06qO2kAiEA+hNLZ/ZhmWdHOwIxGclyAz36MGoD5l3+v/IgRg6sTGI=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@blobatar%2fvue@2.3.1","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":11761},"main":"./dist/index.js","type":"module","types":"./dist/index.d.ts","//check":"No `bun run build` here. The build is a turbo task that `check` depends on, so it runs once for the whole workspace before any check reads a `dist` — a check that rebuilt its own package would delete `dist` out from under a concurrent check in another one.","exports":{".":{"types":"./dist/index.d.ts","default":"./dist/index.js"},"./package.json":"./package.json"},"gitHead":"ddef55dd06dca54274cf525b47fdec37a79d09c4","scripts":{"build":"bun scripts/build.ts","check":"bun run typecheck","prepack":"bun run build","//prepack":"This does not contradict `//check` below, and the difference is who owns the build. Under `check`, turbo owns it: the `build` task runs once for the whole workspace before any check reads a `dist`, so a check that rebuilt its own package would delete one out from under a concurrent check in another. Under `npm pack` and `npm publish` there is no turbo and no ordering — npm runs one lifecycle in one package — so without this the tarball is whatever `dist` happened to be on disk, which for a package built from a peer dependency can be stale, from another branch, or absent entirely. Core carried this from the start; the adapters were published by hand once without it, and only a manual `npm pack --dry-run` caught that the contents were right.","typecheck":"tsc -p tsconfig.json --noEmit"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:e9c45dab-7c9d-4585-b967-3b35266938d5"}},"repository":{"url":"git+https://github.com/Alain00/blobatar.git","type":"git","directory":"packages/vue"},"_npmVersion":"12.0.2","description":"Vue 3 adapter for blobatar — deterministic geometric avatars.","directories":{},"sideEffects":["*.css"],"_nodeVersion":"22.23.2","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"vue":"^3.5.0","blobatar":"workspace:*"},"peerDependencies":{"vue":">=3","blobatar":"2.x"},"//peerDependencies":"`blobatar` is pinned to an exact major, not `^3`. Every package in this set publishes the same version (`.changeset/config.json`), and npm does not enforce that at install time — without the exact range, `@blobatar/react@4` resolves happily alongside `blobatar@3` and renders a different generation's faces from a package the consumer believes is current. Under ADR-0008 the major names the generation, so a mixed pair is not a version skew, it is the wrong picture. `packages/harness` asserts this range rather than trusting it, because release tooling rewrites workspace ranges and would quietly turn it into a caret.","_npmOperationalInternal":{"tmp":"tmp/vue_2.3.1_1787247333793_0.5639084595006301","host":"s3://npm-registry-packages-npm-production"}},"2.4.0":{"name":"@blobatar/vue","version":"2.4.0","keywords":["blobatar","avatar","identicon","vue","svg","deterministic"],"author":{"name":"Alain"},"license":"MIT","_id":"@blobatar/vue@2.4.0","maintainers":[{"name":"alain00","email":"alain00.alvarez@gmail.com"}],"homepage":"https://github.com/Alain00/blobatar#readme","bugs":{"url":"https://github.com/Alain00/blobatar/issues"},"dist":{"shasum":"d7dfe52e61f16fa31eb35a48648172a872510804","tarball":"https://registry.npmjs.org/@blobatar/vue/-/vue-2.4.0.tgz","fileCount":8,"integrity":"sha512-MaxBJOJtzTvkBheEA/CpAeVmLLJNYd/uxxiAjB4fnmBYlHFNsFMwhYDRunQ+2ZnNC/zx+NJWcsnneTYk3J5/rA==","signatures":[{"sig":"MEUCIQC+/xdTsBsZ+/I/KPEBzou9E64NgQ7u/xJwRyhXq+Gg8gIgPMl/IILcQw6lQvbSPefwjxyMaReAYzGeeOW2cldMntQ=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@blobatar%2fvue@2.4.0","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":11761},"main":"./dist/index.js","type":"module","types":"./dist/index.d.ts","//check":"No `bun run build` here. The build is a turbo task that `check` depends on, so it runs once for the whole workspace before any check reads a `dist` — a check that rebuilt its own package would delete `dist` out from under a concurrent check in another one.","exports":{".":{"types":"./dist/index.d.ts","default":"./dist/index.js"},"./package.json":"./package.json"},"gitHead":"16faea0a938f85e0d7612724aafadf98909739e4","scripts":{"build":"bun scripts/build.ts","check":"bun run typecheck","prepack":"bun run build","//prepack":"This does not contradict `//check` below, and the difference is who owns the build. Under `check`, turbo owns it: the `build` task runs once for the whole workspace before any check reads a `dist`, so a check that rebuilt its own package would delete one out from under a concurrent check in another. Under `npm pack` and `npm publish` there is no turbo and no ordering — npm runs one lifecycle in one package — so without this the tarball is whatever `dist` happened to be on disk, which for a package built from a peer dependency can be stale, from another branch, or absent entirely. Core carried this from the start; the adapters were published by hand once without it, and only a manual `npm pack --dry-run` caught that the contents were right.","typecheck":"tsc -p tsconfig.json --noEmit"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:e9c45dab-7c9d-4585-b967-3b35266938d5"}},"repository":{"url":"git+https://github.com/Alain00/blobatar.git","type":"git","directory":"packages/vue"},"_npmVersion":"12.0.2","description":"Vue 3 adapter for blobatar — deterministic geometric avatars.","directories":{},"sideEffects":["*.css"],"_nodeVersion":"22.23.2","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"vue":"^3.5.0","blobatar":"workspace:*"},"peerDependencies":{"vue":">=3","blobatar":"2.x"},"//peerDependencies":"`blobatar` is pinned to an exact major, not `^3`. Every package in this set publishes the same version (`.changeset/config.json`), and npm does not enforce that at install time — without the exact range, `@blobatar/react@4` resolves happily alongside `blobatar@3` and renders a different generation's faces from a package the consumer believes is current. Under ADR-0008 the major names the generation, so a mixed pair is not a version skew, it is the wrong picture. `packages/harness` asserts this range rather than trusting it, because release tooling rewrites workspace ranges and would quietly turn it into a caret.","_npmOperationalInternal":{"tmp":"tmp/vue_2.4.0_1787316812237_0.590839894096953","host":"s3://npm-registry-packages-npm-production"}},"2.5.0":{"name":"@blobatar/vue","version":"2.5.0","keywords":["blobatar","avatar","identicon","vue","svg","deterministic"],"author":{"name":"Alain"},"license":"MIT","_id":"@blobatar/vue@2.5.0","maintainers":[{"name":"alain00","email":"alain00.alvarez@gmail.com"}],"homepage":"https://github.com/Alain00/blobatar#readme","bugs":{"url":"https://github.com/Alain00/blobatar/issues"},"dist":{"shasum":"72bc9287a3cf60e1de70a1fb2c9035f2c68e9b27","tarball":"https://registry.npmjs.org/@blobatar/vue/-/vue-2.5.0.tgz","fileCount":8,"integrity":"sha512-Dl0gmONpPknxCD+j5OooRE5DIMI+oK6lABTGF0de93DSYSqS40XHYQeNI/3olfAJY8160298FnlqEeG7PI6wew==","signatures":[{"sig":"MEUCIETbSM4GEkCCEMftIOwt9zU+A4Qc42hFw6ckthY/KKXyAiEA6q8cMI8Tol+RX7JM3SzBDzd23P7YycjKRYlGXg7sgdI=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@blobatar%2fvue@2.5.0","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":11761},"main":"./dist/index.js","type":"module","types":"./dist/index.d.ts","//check":"No `bun run build` here. The build is a turbo task that `check` depends on, so it runs once for the whole workspace before any check reads a `dist` — a check that rebuilt its own package would delete `dist` out from under a concurrent check in another one.","exports":{".":{"types":"./dist/index.d.ts","default":"./dist/index.js"},"./package.json":"./package.json"},"gitHead":"8fbeea90385311c9d9d6db851f7c6508184dd069","scripts":{"build":"bun scripts/build.ts","check":"bun run typecheck","prepack":"bun run build","//prepack":"This does not contradict `//check` below, and the difference is who owns the build. Under `check`, turbo owns it: the `build` task runs once for the whole workspace before any check reads a `dist`, so a check that rebuilt its own package would delete one out from under a concurrent check in another. Under `npm pack` and `npm publish` there is no turbo and no ordering — npm runs one lifecycle in one package — so without this the tarball is whatever `dist` happened to be on disk, which for a package built from a peer dependency can be stale, from another branch, or absent entirely. Core carried this from the start; the adapters were published by hand once without it, and only a manual `npm pack --dry-run` caught that the contents were right.","typecheck":"tsc -p tsconfig.json --noEmit"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:e9c45dab-7c9d-4585-b967-3b35266938d5"}},"repository":{"url":"git+https://github.com/Alain00/blobatar.git","type":"git","directory":"packages/vue"},"_npmVersion":"12.0.2","description":"Vue 3 adapter for blobatar — deterministic geometric avatars.","directories":{},"sideEffects":["*.css"],"_nodeVersion":"22.23.2","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"vue":"^3.5.0","blobatar":"workspace:*"},"peerDependencies":{"vue":">=3","blobatar":"2.x"},"//peerDependencies":"`blobatar` is pinned to an exact major, not `^3`. Every package in this set publishes the same version (`.changeset/config.json`), and npm does not enforce that at install time — without the exact range, `@blobatar/react@4` resolves happily alongside `blobatar@3` and renders a different generation's faces from a package the consumer believes is current. Under ADR-0008 the major names the generation, so a mixed pair is not a version skew, it is the wrong picture. `packages/harness` asserts this range rather than trusting it, because release tooling rewrites workspace ranges and would quietly turn it into a caret.","_npmOperationalInternal":{"tmp":"tmp/vue_2.5.0_1787506102058_0.7927550223094533","host":"s3://npm-registry-packages-npm-production"}},"2.6.0":{"name":"@blobatar/vue","version":"2.6.0","keywords":["blobatar","avatar","identicon","vue","svg","deterministic"],"author":{"name":"Alain"},"license":"MIT","_id":"@blobatar/vue@2.6.0","maintainers":[{"name":"alain00","email":"alain00.alvarez@gmail.com"}],"homepage":"https://github.com/Alain00/blobatar#readme","bugs":{"url":"https://github.com/Alain00/blobatar/issues"},"dist":{"shasum":"77e98bd8a3a1f780a882557b35d4b7a85edff4df","tarball":"https://registry.npmjs.org/@blobatar/vue/-/vue-2.6.0.tgz","fileCount":8,"integrity":"sha512-xqj2yywv06Xpm4AazM2A/E7Wng7tPnv5VM9FRC79WGueNxzeIRJl4BOHYMi6LJ261r1kGXJ+UgduSsi0tAIpDg==","signatures":[{"sig":"MEUCIFPACrzSeorwiDAEZHPiYYRXbYHEBptPjQN8brRPPVktAiEA3tQA37T8lhtxIf7FFJx0b3Bd3wF4AhCY90GgkVJSgQ8=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@blobatar%2fvue@2.6.0","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":11761},"main":"./dist/index.js","type":"module","types":"./dist/index.d.ts","//check":"No `bun run build` here. The build is a turbo task that `check` depends on, so it runs once for the whole workspace before any check reads a `dist` — a check that rebuilt its own package would delete `dist` out from under a concurrent check in another one.","exports":{".":{"types":"./dist/index.d.ts","default":"./dist/index.js"},"./package.json":"./package.json"},"gitHead":"4f00346f41e17f420e6a00bf2f12ee4d0b4c4772","scripts":{"build":"bun scripts/build.ts","check":"bun run typecheck","prepack":"bun run build","//prepack":"This does not contradict `//check` below, and the difference is who owns the build. Under `check`, turbo owns it: the `build` task runs once for the whole workspace before any check reads a `dist`, so a check that rebuilt its own package would delete one out from under a concurrent check in another. Under `npm pack` and `npm publish` there is no turbo and no ordering — npm runs one lifecycle in one package — so without this the tarball is whatever `dist` happened to be on disk, which for a package built from a peer dependency can be stale, from another branch, or absent entirely. Core carried this from the start; the adapters were published by hand once without it, and only a manual `npm pack --dry-run` caught that the contents were right.","typecheck":"tsc -p tsconfig.json --noEmit"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:e9c45dab-7c9d-4585-b967-3b35266938d5"}},"repository":{"url":"git+https://github.com/Alain00/blobatar.git","type":"git","directory":"packages/vue"},"_npmVersion":"12.0.2","description":"Vue 3 adapter for blobatar — deterministic geometric avatars.","directories":{},"sideEffects":["*.css"],"_nodeVersion":"22.23.2","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"vue":"^3.5.0","blobatar":"workspace:*"},"peerDependencies":{"vue":">=3","blobatar":"2.x"},"//peerDependencies":"`blobatar` is pinned to an exact major, not `^3`. Every package in this set publishes the same version (`.changeset/config.json`), and npm does not enforce that at install time — without the exact range, `@blobatar/react@4` resolves happily alongside `blobatar@3` and renders a different generation's faces from a package the consumer believes is current. Under ADR-0008 the major names the generation, so a mixed pair is not a version skew, it is the wrong picture. `packages/harness` asserts this range rather than trusting it, because release tooling rewrites workspace ranges and would quietly turn it into a caret.","_npmOperationalInternal":{"tmp":"tmp/vue_2.6.0_1787948328184_0.8375128203447655","host":"s3://npm-registry-packages-npm-production"}},"2.7.0":{"name":"@blobatar/vue","version":"2.7.0","description":"Vue 3 adapter for blobatar — deterministic geometric avatars.","type":"module","sideEffects":["*.css"],"main":"./dist/index.js","types":"./dist/index.d.ts","exports":{".":{"types":"./dist/index.d.ts","default":"./dist/index.js"},"./gaze":{"types":"./dist/gaze.d.ts","default":"./dist/gaze.js"},"./package.json":"./package.json"},"publishConfig":{"access":"public"},"scripts":{"build":"bun scripts/build.ts","typecheck":"tsc -p tsconfig.json --noEmit","check":"bun run typecheck","//prepack":"This does not contradict `//check` below, and the difference is who owns the build. Under `check`, turbo owns it: the `build` task runs once for the whole workspace before any check reads a `dist`, so a check that rebuilt its own package would delete one out from under a concurrent check in another. Under `npm pack` and `npm publish` there is no turbo and no ordering — npm runs one lifecycle in one package — so without this the tarball is whatever `dist` happened to be on disk, which for a package built from a peer dependency can be stale, from another branch, or absent entirely. Core carried this from the start; the adapters were published by hand once without it, and only a manual `npm pack --dry-run` caught that the contents were right.","prepack":"bun run build"},"//peerDependencies":"`blobatar` is pinned to an exact major, not `^3`. Every package in this set publishes the same version (`.changeset/config.json`), and npm does not enforce that at install time — without the exact range, `@blobatar/react@4` resolves happily alongside `blobatar@3` and renders a different generation's faces from a package the consumer believes is current. Under ADR-0008 the major names the generation, so a mixed pair is not a version skew, it is the wrong picture. `packages/harness` asserts this range rather than trusting it, because release tooling rewrites workspace ranges and would quietly turn it into a caret.","peerDependencies":{"blobatar":"2.x","vue":">=3"},"devDependencies":{"blobatar":"workspace:*","vue":"^3.5.0"},"keywords":["blobatar","avatar","identicon","vue","svg","deterministic"],"license":"MIT","author":{"name":"Alain"},"repository":{"type":"git","url":"git+https://github.com/Alain00/blobatar.git","directory":"packages/vue"},"homepage":"https://github.com/Alain00/blobatar#readme","bugs":{"url":"https://github.com/Alain00/blobatar/issues"},"//check":"No `bun run build` here. The build is a turbo task that `check` depends on, so it runs once for the whole workspace before any check reads a `dist` — a check that rebuilt its own package would delete `dist` out from under a concurrent check in another one.","gitHead":"ebb7ea4808b1263629fc8fa65e2398b9cbdb6f6b","_id":"@blobatar/vue@2.7.0","_nodeVersion":"22.23.2","_npmVersion":"12.0.2","dist":{"integrity":"sha512-sE417mbyV8cCevxek3LN0M6vx5lCvjjf6wChEE9Fmc3QuMEN6M8yQHM0egMTERVwdAJV+zT78Y4BTiwyxzFEyA==","shasum":"1299def786829e2026ba88f3aee89928391d6ee5","tarball":"https://registry.npmjs.org/@blobatar/vue/-/vue-2.7.0.tgz","fileCount":13,"unpackedSize":27958,"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@blobatar%2fvue@2.7.0","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"signatures":[{"keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U","sig":"MEMCHwm2nUmHAjbiHI7rmsJcs3w+w3gTc6MJOgWNa1McyF8CIC8cMtrS/EckegYCSyRMsOqih+y8IGqwEjCuUizodzDX"}]},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:e9c45dab-7c9d-4585-b967-3b35266938d5"}},"directories":{},"maintainers":[{"name":"alain00","email":"alain00.alvarez@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages-npm-production","tmp":"tmp/vue_2.7.0_1788012097039_0.9857157072137444"},"_hasShrinkwrap":false}},"time":{"created":"2026-08-19T22:40:18.191Z","modified":"2026-08-29T14:01:37.547Z","2.2.0":"2026-08-19T22:40:18.494Z","2.3.0":"2026-08-20T13:22:12.990Z","2.3.1":"2026-08-20T17:35:33.952Z","2.4.0":"2026-08-21T12:53:32.407Z","2.5.0":"2026-08-23T17:28:22.218Z","2.6.0":"2026-08-28T20:18:48.330Z","2.7.0":"2026-08-29T14:01:37.205Z"},"bugs":{"url":"https://github.com/Alain00/blobatar/issues"},"author":{"name":"Alain"},"license":"MIT","homepage":"https://github.com/Alain00/blobatar#readme","keywords":["blobatar","avatar","identicon","vue","svg","deterministic"],"repository":{"type":"git","url":"git+https://github.com/Alain00/blobatar.git","directory":"packages/vue"},"description":"Vue 3 adapter for blobatar — deterministic geometric avatars.","maintainers":[{"name":"alain00","email":"alain00.alvarez@gmail.com"}],"readme":"# @blobatar/vue\n\nVue 3 adapter for [blobatar](https://github.com/Alain00/blobatar) — deterministic\ngeometric avatars generated from any string.\n\n```sh\nbun add @blobatar/vue blobatar\n```\n\n`blobatar` is a peer dependency: the adapter carries no renderer of its own.\n\n```vue\n<script setup lang=\"ts\">\nimport { Blobatar } from \"@blobatar/vue\";\n</script>\n\n<template>\n  <Blobatar :name=\"user.email\" :size=\"48\" />\n</template>\n```\n\nAnimated blobatars need the stylesheet, and render as inline SVG rather than an\n`<img>` — `:hover` never fires inside an `<img>`, so the two modes cannot be\ncombined:\n\n```vue\n<script setup lang=\"ts\">\nimport \"blobatar/motion.css\";\n</script>\n\n<template>\n  <Blobatar :name=\"user.email\" animate=\"hover\" />\n</template>\n```\n\nFull option reference lives in the [main README](https://github.com/Alain00/blobatar#readme).\n\n## Following the pointer\n\nThe eyes can track the cursor. That layer is the one part of the motion system\nthat needs JavaScript, so it is a separate subpath and costs nothing unless you\nimport it:\n\n```vue\n<script setup lang=\"ts\">\nimport { ref } from \"vue\";\nimport { Blobatar } from \"@blobatar/vue\";\nimport { useGaze } from \"@blobatar/vue/gaze\";\nimport \"blobatar/motion.css\";\nimport \"blobatar/gaze.css\"; // required — the eyes hold still without it\n\nconst blob = ref();\nuseGaze(blob, { travel: 3, target: \"pointer\" });\n</script>\n\n<template>\n  <Blobatar ref=\"blob\" :name=\"user.email\" animate=\"always\" :size=\"200\" />\n</template>\n```\n\nIt takes the ref rather than handing one back, because in Vue you already own\nit. What the ref holds is the component instance rather than an element, and the\ncomposable reads `$el` off it — so the same call works if you put the ref on an\n`<svg>` of your own instead.\n\n`travel` is the excursion, and it is what opts a blobatar into the layer:\n`--mo-track-travel` starts at `0px`, so a page with the stylesheet loaded and\nthe excursion set nowhere has a driver running and no eyes moving. It is in\nviewBox units — the blobatar is 100 across, so `3` is 3% of the face — and about\n1.5 to 4 reads well. Leave it out and the stylesheet owns it instead, which is\nthe better route for a whole field of blobatars, since the property inherits, or\nfor anything responsive:\n\n```css\n.hero .mo-eyes { --mo-track-travel: 3px; }\n```\n\nPick one, not both. A rule like that one wins over `travel`, since the option is\nwritten inline on the `<svg>` and reaches the eyes by inheritance.\n\nEverything in the options is read once, when the element arrives. Aiming that\nchanges is `lookAt`, in a watcher of your own:\n\n```ts\nconst { lookAt } = useGaze(blob, { travel: 3 });\nwatchEffect(() => lookAt(watching.value ? \"pointer\" : \"rest\"));\n```\n\nBoth take the same things: a point in client coordinates, an element, `\"pointer\"`\nfor the cursor, `\"rest\"` to park the eyes in the middle without resuming the idle\nglance, or `null` for nothing, which hands it back. The last thing asked for\nwins, whichever asked, and aiming before the blobatar has mounted is remembered\nrather than dropped — so a caret can be driven straight through `lookAt` with no\nre-render per keystroke.\n\n## Versioning\n\nEvery package in the set publishes the same version, and the major names the\n**generation** — the frozen seed-to-look mapping. `@blobatar/vue@2` renders\ngen2, exactly as `blobatar@2` does. Upgrading a major is the opt-in to your\nusers' avatars changing, so the peer range on `blobatar` is an exact major\nrather than `^`: a mixed pair is not a version skew, it is the wrong picture.\n\n## Coming from `blobatar/vue`\n\n`blobatar/vue` still exists and still works. This package re-exports it, so the\ntwo are the same component rather than two copies and cannot drift. That subpath\nis deprecated and is removed in v3 — there is no hurry, and no risk in waiting.\n\n```sh\nbunx blobatar-codemod .\nbun add @blobatar/vue\n```\n\nThe codemod rewrites every `blobatar/vue` specifier it finds, in imports,\n`require`, dynamic `import()` and prose, and is safe to run twice. It does not\ninstall anything; that command is yours.\n","readmeFilename":"README.md"}