Export TS types for data used by specific components

[hongquan]

This allow to import and use type for data under specific components, like:

import { OptionsType } from 'flowbite-vue/components/FwbSelect/types'

Summary by CodeRabbit

• New Features
  • Component types are now publicly exported and can be imported directly from the package.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[netlify]

✅ Deploy Preview for sensational-seahorse-8635f8 ready!

Name	Link
🔨 Latest commit	47ca004
🔍 Latest deploy log	https://app.netlify.com/projects/sensational-seahorse-8635f8/deploys/6961d58ddd7514000851cf0e
😎 Deploy Preview	https://deploy-preview-422--sensational-seahorse-8635f8.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

📝 Walkthrough

Walkthrough

Package.json updated with a new public export mapping. The "./components//types" path is now exported with a corresponding type declaration file reference at "./dist/components//types.d.ts". Three lines added, no lines removed.

Changes

Cohort / File(s)	Summary
Package Configuration package.json	Added new export entry ./components/*/types with type declaration path mapping to ./dist/components/*/types.d.ts

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Hop, hop—exports grow!
Types now flow to all who seek,
Package.json gleams with glee,
A mapping wild and neat!

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Export TS types for data used by specific components' directly and accurately reflects the main change: adding TypeScript type exports in package.json for component-specific types.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 899d684 and 47ca004.

📒 Files selected for processing (1)

• package.json

🔇 Additional comments (1)

package.json (1)

24-26: The export pattern is correctly configured and will generate the expected type declaration files.

The source structure matches the export pattern: each component has a types.ts file (e.g., src/components/FwbButton/types.ts, src/components/FwbSelect/types.ts), and the tsconfig.json specifies outDir: "dist" with includes for src/**/*.ts. The build command vue-tsc --declaration --emitDeclarationOnly && tsc-alias will generate .d.ts files at dist/components/*/types.d.ts, which correctly matches the export mapping. The types are properly exported (e.g., export type OptionsType in FwbSelect), so the import example from the PR description will work correctly.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}