fix(#168): use hast property names for mapped component props

[itsmunzir]

Closes #168

Problem

Attributes of a matched element are passed to the mapped component with their raw DOM attribute names on the client (data-item-id), but with their hast property names on the server (dataItemId). A component like:

<script>
  let { dataItemId } = $props();
</script>

receives the value during SSR, but undefined after initializeComponents runs on the client — so data-* attributes are effectively unreachable.

Fix

initializeComponents now maps placeholder attributes through property-information, so client-side props use the same names as the server (data-item-id → dataItemId, class → className, aria-label → ariaLabel, …). data-component is still excluded. Also documented the prop naming in the component plugin docs.

Verification

The repo has no test suite, so I verified with a scripted repro (jsdom + a compiled Svelte component) running against the built package:

• Before: CSR captured {"data-item-id":"12345"} vs SSR {"dataItemId":"12345"}
• After: CSR captured {"dataItemId":"12345","className":"a b","ariaLabel":"label","href":"/x"} (matches SSR)

Checks: pnpm run lint ✅ · pnpm run check ✅ (0 errors/0 warnings) · pnpm run build ✅ (all packages + docs).

[BearToCode]

Thanks for your contribution ♥️

[github-actions]

🎉 This PR is included in version @cartamd/plugin-component-v1.1.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀