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

@vited/editorconfig

v1.0.1

Published

Recommended EditorConfig for Vited projects

Downloads

5

Readme

@vited/editorconfig

Recommended EditorConfig for Vited projects

root = true

[*]
charset = utf-8
end_of_line = lf
indent_size = 2
indent_style = space
insert_final_newline = true
trim_trailing_whitespace = true
quote_type = single
max_line_length = 100

If you created your project with vited, this editorconfig should already be included. If not, copy above content into your .editorconfig file.

Single quote

By using single quotes, you press less Shift key. It is faster ans healther for your hands.

Print width 100

Tradional 80-character print width is too narrow for modern screen. Considering the smallest common screen usage:

  • 1920x1080 screen with 150% scale, actual width 1280px
  • 2560x1440 screen with splitting, actual with 1280px

If you use VS Code, with side panel, line numbers, scroll mini-map, your actual code area is about 750px. If you use 14px font size (default), you can see about 107 characters. So we think 100 should be a good option for most developers.