Meteor-Community-Packages / Meteor-Community-Packages/template-package
Prepare for 3.0
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 8
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
This is a feature request - we should make this repo 3.0-ready so all new packages will be, too
**Describe the solution you'd like**
In order to easily create new 3.0-compatible packages we should make this repo 3.0 ready first
**Describe alternatives you've considered**
There is no alternative
**Additional context**
-
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 any files, tests, or entry points. Start by reviewing the template package and its CI configuration to determine what “3.0-ready” means for new packages. Define the required compatibility changes and a check that demonstrates a newly created package works before considering this complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100