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

@miroir/eslint-config-svelte

v0.2.0

Published

ESlint config file for strict Svelte(Kit) formatting

Downloads

32

Readme

Custom ES-Lint rules for Svelte & SvelteKit

This is a WIP collection of custom ESLint rules for Svelte and SvelteKit projects inspired by common (and sometimes annoying) mistakes we do and probably can be avoided with some code linting. The main goal is to create a more consistent and predictable development experience, and less time spend on code review.

The rules are very strict by default and can be configured with an extra options object to make them less strict, more flexible, or completely disabled. [WIP]

Installation

npm i -D @miroir/eslint-config-svelte

or

yarn add -D @miroir/eslint-config-svelte

Usage

Add a .eslintrc file to the root of your project with the following content:

{
  "extends": ["@miroir/eslint-config-svelte"],
  "rules": {
    // add custom rules here
  }
}

You may also want to add a .eslintignore file to your project to ignore files and folders from linting:

node_modules
public

Contributing

This is a work in progress. Please feel free to open an issue or a pull request with more custom rules to add.