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

elm-fancy-brunch

v3.0.1

Published

Elm support for brunch, with error display.

Downloads

5

Readme

elm-fancy-brunch

Adds elm support to brunch.

Install

npm install --save-dev elm-fancy-brunch

Usage

The plugin will run automatically. Note that by default no elm files will be compiled unless elm-package.json or brunch-config.js specifies exposed-modules. See below for details.

Configuration

The following defaults can be overridden in brunch-config.js:

{
  ...
  plugins: {
    elm: {
      "exposed-modules": [],
      "source-directories": [],
      compilerOptions {
        debug: true,
        optimize: true
      }
    }
  }
  ...
}

The exposed-modules and source-directories fields correspond to the fields of the same name in elm-package.json and will be parsed from that file if it is present. These two fields determine what modules to compile and where to find them.

Example

If all elm code is kept in web/static/elm and we wish to compile web/static/elm/Main.elm ensure the following configuration is present in elm-package.json or the brunch-config.js plugin configuration:

{
  ...
  "exposed-modules": ["Main"],
  "source-directories": ["web/static/elm"]
  ...
}