npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

svelte-ag

v1.0.45

Published

Useful svelte components

Readme

Exports

There is a browser.ts and index.ts file. There are 2 for the case of things like the vite plugin which use node utils.

Majority of other things will just have an index file eg lib/api/index.ts and its assumed that this is serving the browser

Anything that is only for a node environment will be exported by the index.ts file and this file will only serve node files.

Keeping these separate is required so that we dont have any issues with node trying to import svelte files or svelte trying to import node stuff

Typescript

Although shadcn exists here in the repo it is not shipped. This is simply for tooling and nothing else, as such in the svelte.config.js the aliases are added just for typescript, so that they are not resolved by the packaging process.

This allows consumers to bring their own shadcn components just so long as they resolve $shadcn