Move `ModuleCompatibility` Type to `@nuxt/kit`
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.1k
- Forks
- 354
- Avg merge
- 10h 18m
- Merged PRs (30d)
- 12
Description
Description
The lib/types.ts file contains a // TODO: Move to @nuxt/kit comment for the ModuleCompatibility type.
Moving this type to @nuxt/kit would improve modularity and make it easier to reuse across modules.
https://github.com/nuxt/modules/blob/5346488a2d061c6508cf0df2ad08fe9d9813a9ae/lib/types.ts#L3-L12
Proposed Solution
- Move
ModuleCompatibilitytype definition to@nuxt/kit. - Update any references in the codebase to import
ModuleCompatibilityfrom@nuxt/kit.
Additional Context
Guidance on the preferred location within @nuxt/kit for this type would be appreciated.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with lib/types.ts and locate every reference to ModuleCompatibility in the repository. Inspect @nuxt/kit's existing type exports to determine the appropriate location, then verify that the type is available there and all references import it from @nuxt/kit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxt, typescript
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100