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

@dudeofawesome/create-configs

v2.0.0-23

Published

A script to create configuration files to conform to code style standards.

Downloads

43

Readme

@dudeofawesome/create-configs

A script to create configuration files to conform to code style standards.

Usage

  1. Create your config files.

    $ npm init @dudeofawesome/configs
  2. Answer the prompted questions.

  3. Verify settings match the type of project you're working on.

    ESLint in particular has a bunch of settings that will vary based on the type of project you're working on.

    We provide some other eslint configs for different environments:

Consider adding some editor settings

  • VS Code

    Handled by this script

  • Vim

    let g:prettier#autoformat_config_present = 1
    let g:prettier#autoformat_require_pragma = 0

Consider installing editor plugins

This will automatically apply formatting and linting to your files as you work.

  • VS Code

    Handled by this script

  • Vim

    • https://github.com/prettier/vim-prettier
    • https://github.com/editorconfig/editorconfig-vim
    • https://github.com/vim-syntastic/syntastic
  • IntelliJ IDEA

    • https://www.jetbrains.com/help/idea/prettier.html
    • https://www.jetbrains.com/help/idea/editorconfig.html
    • https://www.jetbrains.com/help/idea/eslint.html
  • Sublime Text

    • https://packagecontrol.io/packages/JsPrettier
    • https://packagecontrol.io/packages/EditorConfig
    • https://github.com/SublimeLinter/SublimeLinter-eslint

Formatting a pre-existing project

If you'd like to maintain git-blame information, you can use the following method (with varying amounts of success):

  1. Make sure you've got a clean working tree

  2. Run Prettier

    prettier -w
  3. Commit changes

    git add .
    git commit --author="Prettier (see commit msg) <[email protected]>" \
    -m "🎨 format with prettier (see message)" -m \
    'To see the original author of a line with `git blame`, use:
    
    ```sh
    git config blame.ignoreRevsFile .git-blame-ignore-revs
    ```
    
    This will configure git to ignore this commit when looking at history for `blame`.'
  4. Add formatting commit hash to .git-blame-ignore-revs

    This makes git blame ignore the formatting commit so you can see the actual author of the line.

  5. Commit .git-blame-ignore-revs

    git add .git-blame-ignore-revs
    git commit -m "🔧 add git-blame-ignore-revs" -m \
    'Run the following command to ignore the repo-wide prettier format
    
    ```sh
    git config blame.ignoreRevsFile .git-blame-ignore-revs
    ```'
  6. Setup git to ignore the formatting commit

    git config blame.ignoreRevsFile .git-blame-ignore-revs