useScriptTikTokPixel: incorrect registery key

[GreenmeisterDavid]

🐛 The bug

There's a bug with the Tiktok Pixel first-party bundling.

useScriptTikTokPixel's derived key is tikTokPixel, but the registry key is tiktokPixel. This uppercase T breaks the lookup and in turn the proxying of the script/calls doesn't work; it falls back to tiktok directly.

🛠️ To reproduce

https://stackblitz.com/edit/github-gzbuzr-k981xdtk?file=app%2Fapp.vue

🌈 Expected behavior

It proxies Tktok Pixel the same way it does other providers (like GA in the linked reproduction)

ℹ️ Additional context

No response

[harlan-zw]

🤖 ISSUE TRIAGE

Harlan Agent Kit posted this automated triage. It is not Harlan's personal assessment or commitment. AI open source policy.

• Route: Ready to implement
• Difficulty: 2/5
• Impact: 3/5
• Reproduction: Yes
• Codebase review: Not needed
• Summary: In packages/script/src/plugins/transform.ts (lines 298-301), the build plugin derives a registry key from the composable name by lowercasing the first character, so useScriptTikTokPixel yields tikTokPixel while the registry key in packages/
• Next action: In packages/script/src/plugins/transform.ts, replace the derived registryKey with registryNode.registryKey from the existing options.scripts lookup (populated for registry composables), then add a failing-first test asserting the TikTok Pixel bundling path resolves the proxy config under tiktokPixel, and verify useScriptYouTubePlayer and useScriptPostHog share the fix.