Skip to main content
VelinStyle v1.3.0
⌂ Home
  1. Docs
  2. Help
  3. Components missing

Docs for VelinStyle 1.3.x · verified against 1.3.0

Components are missing 1.3.0

Confirm the component bundle is loaded and that component APIs match 1.3.0. Deutsch

Problem

Custom elements stay inert, APIs look unknown, or React/Vue props never reach the element.

First check

Run the general diagnostic from the project directory first.

npx @birdapi/velinstyle doctor

Deeper check

npx @birdapi/velinstyle wc api velin-toast
npx @birdapi/velinstyle doctor

Quick check

  • Run commands from the intended project directory.
  • Use only documented profiles and flags.
  • Check again after every change.

Component bundle is not upgraded

Cause: CSS and JS come from different releases, or the IIFE/min bundle is never loaded.

  1. Solution 1: Load dist/velinstyle-components.min.js (or .iife.js) from the same 1.3.0 release as CSS.
  2. Solution 2: Confirm the script runs after the markup that uses the elements.
  3. Solution 3: Re-check with doctor so install and assets agree.
Verify again
npx @birdapi/velinstyle doctor
npx @birdapi/velinstyle check ./index.html --profile docs

Framework props do not match the element API

Cause: The framework wrapper maps props that the custom element does not expose.

  1. Solution 1: Inspect the live API with npx @birdapi/velinstyle wc api velin-toast (swap the tag).
  2. Solution 2: Map only documented attributes/properties from that API.
  3. Solution 3: Keep a minimal HTML reproduction before changing the framework layer.
Verify again
npx @birdapi/velinstyle doctor
npx @birdapi/velinstyle check ./index.html --profile docs

Still broken?

Copy this template into a support request and add the outputs.

BirdAPI Forum · VelinStyle Support