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-add-test

v0.0.1-beta-11

Published

Add functionality to Svelte projects

Readme

❓ What is this?

This is a community project of commands to add particular functionality to Svelte projects.

They are all composable, meaning that it should always be possible to run one after running any other command without something breaking (ideally). This should put an end to the boilerplate problem: too much or too little is included.

🧰 SvelteKit

SvelteKit is an alpha project now, but work is starting now so that there are good integrations for when it enters beta.

💡 Example

To migrate from sapper-firebase-typescript-graphql-tailwindcss-actions-template to SvelteKit, these commands can be run to recreate all the functionality:

# Use the official SvelteKit template
npm init svelte@next  # Say yes to TypeScript preprocessing and select plain CSS

npx apply svelte-add/postcss
npx apply svelte-add/tailwindcss

npx apply svelte-add/graphql

npx apply svelte-add/firebase-hosting
# Actually, there's a limitation for right now that server functions like a GraphQL server
# aren't supported by svelte-add/firebase-hosting, but that could be solved later!

So, to exclude a feature you weren't using that was still included in the boilerplate anyway, don't run its corresponding command. Suppose you only wanted PostCSS and to host on Firebase, then drop the svelte-add/tailwindcss and svelte-add/graphql commands.

🎁 Contributing

This is a community project! Here are some ways you can help:


Repository preview image generated with GitHub Social Preview

This README was generated with ❤️ by readme-md-generator