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

lwp-tools

v0.0.2

Published

Utility scripts for create-lwp based modules.

Downloads

13

Readme

NOTE WELL

This package is pre-release, it's not ready for anyone else to use yet.

This is a module cloned from https://github.com/krakenjs/grumbler-scripts. Props to krakenjs!

The goal is to trim down the dependencies, particularly those with out-of-date dependencies. I've removed the flow-specific stuff, (as I use typescript) and trimed away dependencies that don't pass a yarn audit command.

I have yet to decide to publish it, and not fully updated this README.md

Grumbler Scripts

Shared scripts for grumbler based modules.

Package.json scripts

 "scripts": {
    "setup": "npm install",
    "lint": "eslint --ext js,jsx config/ test/ *.js",
    "babel": "babel ./config --ignore=node_modules --out-dir ./config",
    "webpack": "babel-node --plugins=transform-es2015-modules-commonjs ./node_modules/.bin/webpack --progress",
    "test": "npm run lint && npm run test-babel && npm run test-webpack && npm run find-eslint-rules",
    "build": "npm run test && npm run babel && npm run webpack ",
    "release": "./publish.sh",
    "release:patch": "./publish.sh patch",
    "release:minor": "./publish.sh minor",
    "release:major": "./publish.sh major",
    "clean": "rimraf dist coverage",
    "reinstall": "rimraf node_modules && npm install",
    "debug": "cross-env NODE_ENV=debug",
    "prepublish": "in-publish && npm run babel || not-in-publish",
    "postpublish": "git checkout config",
    "test-babel": "babel --config-file ./config/.babelrc-node test/* > /dev/null && babel --config-file ./config/.babelrc-browser test/* > /dev/null",
    "test-webpack": "babel-node --plugins=transform-es2015-modules-commonjs ./node_modules/.bin/webpack --progress",
    "check-updates": "npm-check-updates"
  }

ESLint

.eslintrc.js

Node

module.exports = {
  extends: "./node_modules/ts-lib-scripts/config/.eslintrc-node.js"
};

Browser

module.exports = {
  extends: "./node_modules/ts-lib-scripts/config/.eslintrc-browser.js"
};

Babel

.babelrc

Node

{
  "extends": "ts-lib-scripts/config/.babelrc-node"
}

Browser

{
  "extends": "ts-lib-scripts/config/.babelrc-browser"
}

Webpack

webpack.config.js

import { getWebpackConfig } from "ts-lib-scripts/config/webpack.config";

const FILE_NAME = "mylibrary";
const MODULE_NAME = "mylibrary";

export let WEBPACK_CONFIG = getWebpackConfig({
  filename: `${FILE_NAME}.min.js`,
  modulename: MODULE_NAME,
  minify: true
});

export default [WEBPACK_CONFIG];

Karma

karma.conf.js

import { getKarmaConfig } from "ts-lib-scripts/config/karma.conf";
import { getWebpackConfig } from "ts-lib-scripts/config/webpack.config";

export default (karma: Object) =>
  karma.set(
    getKarmaConfig(karma, {
      basePath: __dirname,
      webpack: getWebpackConfig()
    })
  );