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

@wasc/tools

v5.15.5

Published

# [![wasc-tools](docs/carbon.png)](https://github.com/wasc-io/tools)

Downloads

307

Readme

\wasc-tools\

wasc-tools

Opinionated toolkit for every JavaScript project in need 🚨

Installation

Install in your project:

yarn add -D @wasc/tools

Usage

This tool is straight-forward: it transpiles with, it lints, it pretties, it tests and it even counts lines of code. All behind an easy cli. For big projects we recommend to use the tool inside the package.json's scripts-tag:

"scripts": {
    "start": "wasc-tools watch --debug",
    "build": "wasc-tools build",
    "lint": "wasc-tools lint",
    "format": "wasc-tools format",
    "test": "wasc-tools test",
    "count": "wasc-tools count",
}

!!! IMPORTANT Note

For usage with the integrated start and build commands, you need to install the package source-map-support. It replaces all stacktraces, with resolved locations from the compiled source maps.

Usage with IDE tooling

The project exports a prettier.js and eslint.js file with the accepted configurations. In your project just add an .eslintrc.js file:

module.exports = require('@wasc/tools/eslint');

and a prettier.config.js:

module.exports = require('@wasc/tools/prettier');

Preact-cli presets

This exports preact-cli configuration snippets, they can be imported for a preact.config.js file:

import { graphql } from '@wasc/tools/preact';

export default function (...args) {
  // Allows .graphql-file imports in your preact-project
  graphql(...args);
}

We include:

  • graphql(): import .graphql files
  • markdown(): import .md file which are compiled to HTML at build time
  • compression(): compresses the output bundles with gzip and brotli to serve static precompressed file with nginx for example
  • staticFiles(): statically copies robots.txt and security.txt files to the output root and .well-known/security.txt respectivly
  • babel(): adds optional-chaining and transform-react-jsx-source plugins to babel
  • typescript(): allows for ts/tsx entrypoint files

Changelog