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 🙏

© 2025 – Pkg Stats / Ryan Hefner

webstorm-init

v0.0.3

Published

CLI tool to write initial WebStorm settings into a new project

Downloads

11

Readme

webstorm-init

CLI tool to write initial WebStorm settings into a new project

Requirements

The build-in templates may require WebStorm 2020.1 or newer. NodeJS 10 or newer required. You can use webstorm-init in Windows Powershell, Linux and MacOS.

Installation

You should install webstorm-init globally to easily access it from any project folder:

npm i -g webstorm-init

Usage

  • in your shell cd into your project's folder
  • run webstorm-init or wsi

Options

 Option          | Description
 --------------- | ---------------------------------------------------
 -f, --force     | prompt to overwrite existing WebStorm config folder
                 |
 -h, --help      | show built-in help page
                 |
 -t, --template  | path to be used as template.
                 | Defaults to the user's home directory, or the
                 | built-in template, if ~/.idea_template does not exist.
                 |
 -v, --version   | show version info

Templates

There are three ways to influence how webstorm-init is setting up the .idea folder:

  • use the --template command line parameter to specify a project directory, e.g.
    webstorm-init --template c:\dev\myproject or on Linux/Mac: webstorm-init --template ~/dev/myproject
  • create a template folder in your home directory and put a .idea folder there to be used as template: c:\users\myname\.idea_template\.idea or on Linux/Mac: ~/.idea_template/.idea
  • skip both steps, then webstorm-init uses its built-in template (default)

Built-In settings

The built-in project settings are rather opinionated any optimized to match my workflows. Use a custom template to define your own settings.

  • Language & Frameworks > JavaScript > Prettier:
    • use Prettier package supplied by the project
    • Run for files on code reformat and on save
  • Language & Frameworks > JavaScript > Code Quality Tools > ESLint:
    • Automatic ESLint configuration
    • Run eslint --fix on save
  • Editor > Inspections: Turn off all JavaScript and TypeScript inspections
  • Editor > Code Style > JavaScript > Imports
    • Merge imports for members of the same module
    • Use paths relative to the project, resource or sources roots
  • Editor > Code Style > TypeScript > Imports
    • Use paths relatvie to tsconfig.json
  • Misc: mark the project's src folder as Resource Root

Limitations

WebStorm manages a second workspace file in your profile directory to manage open files and folders opened in the project browser. These files need a project specific unique ID. webstorm-init cannot recreate this ID, i.e. WebStorm will start with a blank view and a collapsed project tree for new projects. When overwriting existing settings the project id is retained.

Disclaimer

Using this tool will overwrite some or all files in the current folder's .idea directory! Use at your own risk.

License

Licensed under MIT