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

kompiler

v7.0.164

Published

A framework agnostic compiler/transpiler. For personal use and for friends. Forever work in progress.

Downloads

259

Readme

kompiler

A framework agnostic compiler/transpiler. For personal use and for friends. Forever work in progress.

Options

In package.json at the key kompiler you may use the following options

// pacakge.json

{
  "kompiler": {
    // restart the whole thing when something changes, for babel plugins that change
    "watch": [],
    // enviroment
    "env": {
      "NODE_ENV": "development/production",
    },
    // an array of "node scripts" to run, watch, and automatically restart
    "node": [
      {
        // the dirname of "input" is automatically watched for restarting the node script
        "input": "socket/index.js",

        // in case you have a folder or file you want to watch that is outside "input" folder to restart the script. Useful for developing npm packages using "npm link"
        "watch": [],
      },
    ],
    // for all builds:
    "map": [
      // for mapping paths served by the static server for all builds
      ["S:/www/aa/client/npm/package/", "S:/www/npm/package/"],
    ],
    // babel config for all builds
    "babel": {
      "presets": ["solid"],
    },
    // similar to node property is for running rollup, as many as you want
    "builds": [
      {
        // input file to process, a "static file server" is fired on this folder
        "input": ["client/index.js"],
        // where to put the output, if the output is a folder is will use multi-entry
        // file will be client/dist/multi-entry.js instead when folder a folder is used here
        "output": "client/dist/index.m.js",
        // if output should be minified and treeshaked
        "minified": false,
        // useful for when testing video that chrome does 206 requests, express is slow the compiler use a faster server but doesnt support 206
        "express": false,
        // server document root, set to `false` to not start a static file server
        "root": "./",

        // for opening a special page when loading the server
        "page": "index.html",
        "hostname": "localhost",
        // babel config
        "babel": {
          "presets": ["solid"],
        },
        // in case you have a folder or file you want to watch that is outside "input" folder. Useful for developing npm packages using "npm link". It will trigger a rebuild and possible an update on the browser if anything changes
        "watch": [],
        // for mapping paths served by the static server
        "map": [["S:/www/aa/client/npm/package/", "S:/www/npm/package/"]],
        // rollup options, if any
        "rollup": {},
      },
    ],
    // legacy stuff, if you need a file from the web and you want to automatically update it this will do it. It checks at most 1 time per day and only if the compiler is running
    "autoupdates": [["https://www.example.net/jquery@3", "client/js/jquery.js"]],
  },
}