vitejs/vite-plugin-react-pages
First read
Useful directional context, not a final verdict yet
vitejs/vite-plugin-react-pages is better read as a directional signal than a clean recommendation. Keep the snapshot conservative and validate source activity, package reality, and close alternatives before committing to it.
470 public stars in the current GitStar snapshot.
Needs a narrower context read
Last commit Dec 12, 2025.
Stale activity
Treat stars as discovery context until a linked package appears.
No linked package mapping
One or more key signals are partial, so GitStar keeps the interpretation conservative.
Partial snapshot
Snapshot facts
- 470 stars
- 71 forks
- Last commit Dec 12, 2025
- Package usage not mapped yet
Compare lens
shadcn-ui/ui and vercel/next.js are the closest comparison targets GitStar found. A side-by-side comparison usually tells you more than a single raw rank.
Signal trail
Trajectory
Read the recent motion first. This block is for deciding whether the repository still looks alive, compounding, or flattening before you trust stars alone.
Package reality
No linked npm or PyPI package is mapped for this repository yet, so the page leans more heavily on GitHub-visible popularity and should be read more conservatively.
GitStar expects a package signal here, but no npm or PyPI package is linked to this repository yet.
Validation note
GitStar can summarize public signals for vitejs/vite-plugin-react-pages, but the GitHub repository is still the primary place to confirm release cadence, issue activity, and maintainer intent.
GitStar surfaces public popularity and package signals. These rankings are not endorsements, security reviews, or investment advice.
Why this rank
This repo is here because it still carries strong GitHub attention.
Reconstructed from current stars and cached daily/weekly/monthly deltas.
GitStar can see repository momentum, but it does not have a reliable linked package signal yet.
Treat stars and recent movement as discovery context only until npm or PyPI usage is available.
shadcn-ui/ui
Shares the frameworks category footprint with vitejs/vite-plugin-react-pages, so the comparison is closer to a same-problem decision than a same-language coincidence.
vercel/next.js
Shares the frameworks category footprint with vitejs/vite-plugin-react-pages, so the comparison is closer to a same-problem decision than a same-language coincidence.
facebook/react-native
Shares the frameworks category footprint with vitejs/vite-plugin-react-pages, so the comparison is closer to a same-problem decision than a same-language coincidence.
vuejs/vue
Shares the frameworks category footprint with vitejs/vite-plugin-react-pages, so the comparison is closer to a same-problem decision than a same-language coincidence.
Cross-links
GitStar picked ui + next.js as the closest next comparison from the related repository set.
Embed Badge
[](https://gitstar.space/repo/vitejs/vite-plugin-react-pages)<a href="https://gitstar.space/repo/vitejs/vite-plugin-react-pages"><img src="https://gitstar.space/api/badge/vitejs/vite-plugin-react-pages" alt="GitStar"></a>🔗 Wider nearby ecosystem
A set of beautifully-designed, accessible components and a code distribution platform. Works with your favorite frameworks. Open Source. Open Code.
The React Framework
A framework for building native applications using React
This is the repo for Vue 2. For Vue 3, go to https://github.com/vuejs/core
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
Production-ready platform for agentic workflow development.
Next step after the validation read
Learn and methodology
About This Page
This page provides a quick overview of vitejs/vite-plugin-react-pages based on GitStar's cached data. The signal chart reconstructs approximate checkpoints from current stars plus cached daily, weekly, and monthly star deltas, so it is best read as directional context rather than as a precise historical audit log.
Want to show your project's ranking? Copy the badge embed code above and add it to your README.