🤔 what i was thinking of was having the experience of using next.js routing in react

🤔 what i was thinking of was having the experience of using next.js routing in react 🚀 therefore upcoming.js — was born if you use React + Vite you know this pain. every new project. every new route. same boilerplate: } /> } /> } /> every. single. time. meanwhile Next.js developers just create a folder and the route exists. no imports. no declarations. nothing. i wanted that. but i didn't want Next.js. i wanted React. i wanted Vite. i wanted freedom. so i built upcoming.js. a Vite plugin that brings Next.js-style file routing to any React + Vite project. no framework. no lock-in. just the one feature that actually matters. src/ ├── page.jsx → / ├── about/ │ └── page.jsx → /about └── blog/ └── [id]/ └── page.jsx → /blog/:id that's your entire router. create a folder → route appears instantly. delete a folder → route is gone. no restarts. no imports. no boilerplate. ever. and since it's built on React Router under the hood — useParams, useNavigate, Link — everything works exactly the way