Update npm latest tag to point to Beta v3
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.1k
- Forks
- 466
- Avg merge
- 2d 31m
- Merged PRs (30d)
- 13
Description
Describe the bug
Currently, tanstack virtual installs by default the alpha version.
Your minimal, reproducible example
Steps to reproduce
npm i @tanstack/virtual
Expected behavior
The latest Beta version is installed.
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform
tanstack-virtual version
3.0.0-alpha.0
TypeScript version
No response
Additional context
No response
Terms & Code of Conduct
- I agree to follow this project's Code of Conduct
- I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.
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 checking the package publishing configuration for @tanstack/virtual and how its npm tags are assigned. Run npm i @tanstack/virtual before and after the change to verify that the latest Beta version, rather than the alpha version, is installed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- release
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100