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

@whiletruu/format-elm-webpack-errors

v1.0.4

Published

Colours and formats elm compiler error messages in json format it finds in webpack errors.

Downloads

3

Readme

format-elm-webpack-errors Version Elm version

Colours and formats elm compiler error messages in json format it finds in webpack errors.

Elm compiler errors are easy to understand and useful (https://elm-lang.org/blog/compiler-errors-for-humans). However, elm make outputs uncoloured error messages when stdout is not a terminal (https://github.com/elm-community/elm-webpack-loader/issues/94) and this looks ugly, makes longer error messages harder to navigate and understand at a glance and clutters them with useless internal stacks.

Default error messages:

unformatted

Messages formatted with this package:

formatted

Install

npm install @whiletruu/format-elm-webpack-errors --save-dev

Usage

Report elm compiler errors as json.

{
  loader: require.resolve("elm-webpack-loader"),
  options: { report: "json" }
}

Create a webpack compiler for WebpackDevServer

const webpack = require("webpack");
const formatElmCompilerError = require("@whiletruu/format-elm-webpack-errors");

const compiler = webpack(/* config */);

function isElmCompilerError(error) {
  return error.startsWith("./src/Main.elm");
}

compiler.hooks.invalid.tap("invalid", function() {
  console.log("Compiling...");
});

compiler.hooks.done.tap("done", stats => {
  const { warnings, errors } = stats.toJson({
    all: false,
    warnings: true,
    errors: true
  });

  const messages = {
    warnings,
    errors: errors.map(error =>
      isElmCompilerError(error) ? formatElmCompilerError(error) : error
    )
  };

  if (!messages.errors.length && !messages.warnings.length) {
    console.log(chalk.green("Compiled successfully!"));
  }

  if (messages.errors.length) {
    console.log(chalk.red("Failed to compile.\n"));
    console.log(messages.errors.join("\n\n"));
    return;
  }

  if (messages.warnings.length) {
    console.log(chalk.yellow("Compiled with warnings.\n"));
    console.log(messages.warnings.join("\n\n"));
  }
});

WebpackDevServer has it's own messages by default, but now we're emitting ours by listening to the compiler events with compiler.hooks[...].tap. To not get the same errors several times in different formats, WebpackDevServer should be told to be quiet in it's config.

{
  quiet: true;
}