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

lerna-script-tasks-idea

v1.4.0

Published

task for start that generates intellij project for repo

Downloads

49

Readme

lerna-script-tasks-idea

lerna-script task to generate WebStorm project for a Lerna managed project with hardcoded conventions:

  • mark node_modules as ignored so WebStorm would not index those. Having >= 20 modules open with node_modules indexing pretty much kills it:/
  • set source level to es6;
  • mark lib, src as source rootps and test, tests as test roots;
  • add mocha run configurations for all modules.

Note: given this task generates WebStorm project files manually, you must close all instances of WebStorm before generating and open afterwards.

install

npm install --save-dev lerna-script-tasks-idea

Usage

Add lerna-script launcher to package.json scripts:

{
  "scripts": {
    "start": "lerna-script"
  }
}

Add export to lerna.js:

const idea = require('lerna-script-tasks-idea');

module.exports.idea = idea();

To generate WebStorm project run:

npm start idea

API

({[packages], mochaConfigurations: packageJson => [], excludePatterns, addRoot: boolean = false})(log): Promise

Returns a function that generates WebStorm for all modules in repo.

Parameters:

  • packages - list of packages to generate idea project for or defaults to ones defined in lerna.json;
  • mochaConfigurations - function, that, given packageJson object of a module returns a list of mocha configurations in a format:
    • name - configuration name;
    • environmentVariables - key/value pair of environment variables for configuration;
    • extraOptions - extra mocha options;
    • testKind - kind of test, ex. PATTERN;
    • testPattern - pattern expression.
  • excludePatterns - array of patterns that will be set as the project exclude patterns. Files\Folders matching that pattern will be marked as "excluded" in Idea
  • addRoot - when true, the root.iml file will be generated to make all non-modules visible in IDEA (optional, defaults to false)
  • log - npmlog instance.