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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@jwrunner/svelte-ui

v0.1.0

Published

Useful Svelte UI components shared across projects with some TW styles

Downloads

12

Readme

Svelte-Ui

To install components that I use across projects you can run npm i -D @jwrunner/svelte-ui though because svelte-kit package is still buggy with not all components being typed properly (Store.svelte use of the new $$Generic type cause the type-creator to skip that component for example), I presently just copy components into a mirrored src/shared directory in my projects to use components.

To update NPM package

Run npm version patch which will bump from 1.0.2 to 1.0.3 for example and then commit the changes, and push changes to GitHub which will automatically fire off an NPM publish

To develop using Svench (like Storybook)

Run npx svench - note that sometimes you have to run npx svench a couple times before it will fire up (bug). Do note that if it just hangs with no luck after multiple tries, then you have induced a syntax error. It won't tell you about the error but if you undo your changes and things fire up then you just have to dig in and find the error.

Preview

Run npx svench build and npx sirv-cli /.svench/build to preview locally or view at https://jwrunner-svelte-ui.vercel.app/.

Components TODO

CKEditor