fix: include all source files for type declaration

[jhoward1994]

What does it do?

Updates the include option for the vite-plugin-dts plugin to match all source files within the entry file's directory, using path.join(path.dirname(bundle.source), '**/*'). This expands type declaration generation from just the entry file to all files in the source folder.

Why is it needed?

By including all source files, all relevant type declarations will be emitted.

How to test it

1. Create a Strapi plugin with TypeScript types spread across multiple files (e.g., with types imported from sibling modules).
2. Build the plugin using strapi-plugin build.
3. Check that the generated dist types directory includes declaration files for all referenced and imported types, not just for the entry point.

Related issue(s) / PR(s)

#115

[changeset-bot]

🦋 Changeset detected

Latest commit: 69f6aba

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@strapi/sdk-plugin	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[dosubot]

Related Documentation

1 document(s) may need updating based on files changed in this PR:

Strapi

development /documentation/blob/main/docusaurus/docs/cms/typescript/development.md

View Suggested Changes

@@ -149,3 +149,7 @@
 :::note
 It is not necessary to repeat the `yarn` or `npm install` command after the initial installation. The `yarn build` or `npm run build` command is necessary to implement any plugin development that affects the admin panel.
 :::
+
+### Type declaration generation
+
+When building TypeScript plugins using the Plugin SDK (`yarn build` or `npm run build`), the build process generates comprehensive type declarations for all source files in the plugin, not just the entry point. All TypeScript types, interfaces, and type definitions used throughout the plugin will have corresponding `.d.ts` declaration files emitted in the build output. This ensures better TypeScript support and IDE autocomplete for developers consuming the plugin.

[Accept] [Decline]

Note: You must be authenticated to accept/decline updates.

^{How did I do? Any feedback?}  

[boazpoolman]

Hi @jhoward1994,

I've approved the PR because it solves #115 effectively.

However, there is a related types problem I see with custom exports. For example this Better Auth plugin. It has a custom export called 'adapter' which doesn't get any types in the build directory, even though they are specified in the exports object.

[jhoward1994]

@boazpoolman thanks will look into that as a follow up