Bridge Vite integrations Improvements
Open
Nobody has claimed this yet.
enhancement
vite
- Dominant language
- TypeScript
- Stars
- 285
- Forks
- 33
- Avg merge
- 22h 38m
- Merged PRs (30d)
- 3
Description
Meta issue to track the progress from https://github.com/nuxt/framework/pull/1180
-
Update mocks with unenv(~> nuxt/nuxt.js#12786) - Opt-in legacy
- Hide invalid component name warnings (does it happens for external package too?)
- Remove defaultexport workaround (needs fix on nuxt/components)
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
Read the linked nuxt/framework pull request #1180 and the referenced nuxt/nuxt.js#12786 issue first. Then review each checklist item: unenv mocks, opt-in legacy behavior, invalid component-name warnings, and the defaultexport workaround. Done means the listed integration improvements are resolved and the checklist can be completed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vite
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100