Community template support for `init` command
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 10.5k
- Forks
- 564
- PR merge metrics
- No merged PRs in 30d
Description
I've consistently said no to adding content to the templates:
- https://github.com/wxt-dev/wxt/issues/552
- https://github.com/wxt-dev/wxt/issues/325
- https://github.com/wxt-dev/wxt/issues/369
- https://github.com/wxt-dev/wxt/issues/187
Templates are a huge time sink to keep up to date and the more features/variants that are added, the more time it takes away from me to add features and fixes to WXT itself.
That said, I'm open to adding community template support to the init command!
Originally posted by @aklinker1 in https://github.com/wxt-dev/wxt/issues/570#issuecomment-2214057163
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
The issue does not name files or tests. Start by locating the init command and its existing template handling, then clarify how community templates should be discovered, selected, and maintained. Done should mean the agreed community-template workflow is supported by init and covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100