Use a different tag for unstable npm packages
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 45
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
From TD Call of 02.08:
- Luca: This is wrong semver. If we use date, it would be better to use ISO date format. For future versions, we can use
_pre20231223to be more aligned with common practices.
Originally posted by @egekorkan in https://github.com/w3c/wot-thing-description/issues/1863#issuecomment-1662415530
As @lu-zero mentioned is better to use the ISO date format because it maintains the lexical graphical order (this makes npm install work also with pre-releases). After the 1.1.0 publication, we can switch to this new approach.
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 by locating the npm package version and distribution-tag configuration in the repository, then review how the current unstable versions are generated. Confirm the ISO date format and the proposed _preYYYYMMDD convention against npm prerelease behavior; done means unstable packages use the new convention after the 1.1.0 publication.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100