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

format-webpack-stats-errors-warnings

v2.1.0

Published

A normalized format for webpack's errors and warnings

Downloads

6

Readme

About this

A normalized format for webpack's errors and warnings.

Webpack's error output is very verbose. However, I found it is diffcult to match it when I was using vscode. So I create this package to reformat the webpack's errors and warnings.

Install

npm install --save-dev format-webpack-stats-errors-warnings

How to use:

It is really simple, just use it in your webpack's callback function. Here is an example:

webpack(webpackConfig, function (err, stats) {
    if (err) {
        console.error(err)
        throw err
    }
    
    // add this package here:
    console.log(require('format-webpack-stats-errors-warnings')(stats, config.PROJECT_ROOT))

    // You can still output the verbose default webpack's output
    process.stdout.write(stats.toString({
            colors: !!+process.env.DISABLE_OUTPUT_COLOR,
            modules: false,
            children: false,
            chunks: false,
            chunkModules: false
        }) + '\n')
})

parameters:

  • stats: The second parameter of webpack callback function.
  • projectRoot: The root path of your project. It is used to make output path be relative. If omitted, the output path will be absolute.

return:

  • A formatted string. You must output it yourself.

Difference with webpack's default output

Webpack's:

Module not found: Error: Can't resolve 'something-not-exists' in 'xxxx\src'
 @ xxxxr/~/.6.4.0@babel-loader/lib!./~/.11.1.4@vue-loader/lib/selector.js?type=script&index=0!./src/App.vue 11:0-30
 @ ./src/App.vue
 @ ./src/main.js

This package's:

!>error: src\App.vue:32,13~33: Module not found: Error: Can't resolve 'something-not-exists' in 'xxxx\src'

Note: this package combined all errors into one line, and add line number and column number.

problemMatcher for vscode:

You can use the following as problemMatcher in your tasks.json of vscode

{
    "owner": "webpack",
    "fileLocation": [
        "relative",
        "${workspaceRoot}"
    ],
    "pattern": {
        "regexp": "^!>(\\w+): (\\S+)?:(\\d+),(\\d+)(?:~(?:(\\d+),)?(\\d+))?: (.*)$",
        "severity": 1,
        "file": 2,
        "line": 3,
        "column": 4,
        "endLine": 5,
        "endColumn": 6,
        "message": 7
    }
}