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

jetbrains-project

v0.0.4

Published

Utilities for working with JavaScript projects (and monorepos) in JetBrains IDEs (IntelliJ, WebStorm, etc.).

Downloads

3

Readme

jetbrains-project

Utilities for working with JavaScript projects (and monorepos) in JetBrains IDEs (IntelliJ, WebStorm, etc.).

Highlights

  • Efficient file watcher to exclude certain dirs from indexing as they are created to prevent IDE locking up.

Try

npx jetbrains-project

Install

npm i -g jetbrains-project

Usage

cd your-intellij-project-dir
jetbrains-project update

Watch an IntelliJ project folder for when new folders are created, and automatically exclude their node_modules and other generated dirs you specify such as lib, build, etc.

Features

Excluding node_modules

Once the IntelliJ indexer starts it cannot be stopped and will max out your cpus until its finished. See here for some discussion.

IntelliJ only indexes direct dependencies as of v2016.2.2 (see issue), that is, those defined in your package.json.

If we use a mono-project (i.e. one IntelliJ project/module with multiple packages inside), we may end up with a huge number of dependency files to index.

node_modules dirs can easily grow to 100K+ files even when installing one module, which will take ages to index.

Installing a single module will cause indexing, which will slow down the IDE.

The following IntelliJ issue would resolve this: Ability to exclude files from indexing in a path by their names (full paths) or by pattern.

The following issues are also related:

If the IntelliJ cache becomes corrupt (e.g. after an improper shutdown), you will have to wait ages for it to re-index.

License

MIT © Vaughan Rouesnel