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

@superkoders/prettier-config

v0.2.6

Published

SUPERKODERS prettier configuration

Downloads

1,724

Readme

@superkoders/prettier-config

SK shareable prettier config, which is prepared for use with our eslint configuration

Instalation

1. Install the package

npm i -D @superkoders/prettier-config

2. Add .prettierrc.js

This tells prettier where to locate our rules. You can also override the rules here, if you have some exception on a given project.

module.exports = {
	...require('@superkoders/prettier-config'),
};

If you need to make special overrides for given project, you can do so like this:

module.exports = {
	...require('@superkoders/prettier-config'),
	useTabs: true // you can add overrides like so
};

3. Add .prettierignore

Specify paths and files you don't want to autoformat. Be sure to ignore minified 3rd party files. Good starting point might be this:

*.md
*.mdown
*.mdx
package.json
package-lock.json
web/*
src/js/static/*
**/node_modules/**/*

4. Add .gitattributes file

Make sure, that line endings will be same accross platforms / OS. This line will make the magic:

* text eol=lf

5. Optional: Live error/warning highlightning with editor extension

Download an extension, which will highlight problematic code and give you options how to fix it or which will auto format it as you save. Prettier do VS Code

6. Update VS Code settings for autoformatting

Ideally, save those settings in .vscode/settings.json so it lives with the project, if it isn't there already.

"editor.formatOnSave": true,
"prettier.requireConfig": true, // Only format configured projects