WarningImHack3r / svelte-changelog

svelte-changelog svelte-changelog.dev Made with SvelteKit, TailwindCSS & shadcn-svelte. Features • Gorgeous UI from shadcn/ui • Includes _all_ NPM packages by the Svelte team that can be used in a project • Track the relevant repos' PRs, issues, and discussions • Stunning page embedding all details of a pull request/issue/discussion • RSS feeds for all packages • Dynamically computed badges to indicate whether a package is the Latest, a Major version, a Prerelease, or a Maintenance version • Sidebar with the number of unseen releases for each package • ...and much more! How does it work? The site makes requests to the GitHub API on the server side to get the latest releases for all the packages. It smartly caches the data, frequently invalidating it to always be up to date while avoiding hitting GitHub as much as possible. Whilst the repos are manually curated, the packages are automatically discovered, either through the published releases or the contents of the file. Some computations are made to generate the badges, but everything else is a simple cosmetic wrapper around GitHub releases. **No data alteration is performed by the site other than for styling and rendering purposes**. For more info, visit the v2 release post. Run locally That's it: your GitHub token will do most of the job, and you can run the website like any regular SvelteKit app. Environment Variables • : a classic GitHub token with the scope (that's it), required for API requests. • (optional): the TCP URL for the Redis instance. You can leave it empty; an in-memory cache is used during development. • (optional): the token for the analytics service I use, PostHog. You can leave it empty; analytics are disabled in dev environments. • (optional): the token for webhook reception, not useful in a dev environment but has to be present still. Missing a repository? If you think I missed a repository, you can either open an issue or directly contribute. Repository inclusion criteria • Must be by the Svelte team or their members • Must be on GitHub • Must _not_ be an internal repo/package used only by the Svelte team • Must either have releases on GitHub or at least have tags and a file at the root of the repository How to contribute Fork the repo, edit the file, and open a PR. The site's code has been architectured to be as flexible as possible, here's how it works: Add your repo where you see fit (tools or libs), and that's it! The site will automatically discover & adapt to the new package(s).