Version Drift
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 2.1k
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Description
Hi there, great tool. Thanks for your hard work on this. I use this in my static site generator.
I was doing some updates and noticed that the npm package is 2 years old. Is there much version drift between the published package and github?
Many thanks.
Contributor guide
No contributing guide indexed for this repository
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
Compare the published npm package with the GitHub repository and inspect the available version or release metadata. Confirm whether the package is behind the repository, then document the version difference and current release status.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100