webpack / analyse

analyse web app for webpack stats

webpack

Webpack is a module bundler. Its main purpose is to bundle JavaScript files for usage in a browser, yet it is also capable of transforming, bundling, or packaging just about any resource or asset.

Table of Contents

1. Install
2. Introduction
3. Concepts
4. Contributing
5. Support
6. Core Team
7. Sponsoring
8. Premium Partners
9. Other Backers and Sponsors
10. Gold Sponsors
11. Silver Sponsors
12. Bronze Sponsors
13. Backers
14. Special Thanks

Install

Install with npm:

npm install --save-dev webpack

Install with yarn:

yarn add webpack --dev

Introduction

Webpack is a bundler for modules. The main purpose is to bundle JavaScript files for usage in a browser, yet it is also capable of transforming, bundling, or packaging just about any resource or asset.

TL;DR

• Bundles ES Modules, CommonJS, and AMD modules (even combined).
• Can create a single bundle or multiple chunks that are asynchronously loaded at runtime (to reduce initial loading time).
• Dependencies are resolved during compilation, reducing the runtime size.
• Loaders can preprocess files while compiling, e.g. TypeScript to JavaScript, Handlebars strings to compiled functions, images to Base64, etc.
• Highly modular plugin system to do whatever else your application requires.

Get Started

Check out webpack's quick Get Started guide and the other guides.

Browser Compatibility

Webpack supports all browsers that are ES5-compliant (IE8 and below are not supported). Webpack also needs Promise for import() and require.ensure(). If you want to support older browsers, you will need to load a polyfill before using these expressions.

Concepts

Plugins

Webpack has a rich plugin interface. Most of the features within webpack itself use this plugin interface. This makes webpack very flexible.

Name	Status	Install Size	Description
mini-css-extract-plugin			Extracts CSS into separate files. It creates a CSS file per JS file which contains CSS.
compression-webpack-plugin			Prepares compressed versions of assets to serve them with Content-Encoding
html-webpack-plugin			Simplifies creation of HTML files (index.html) to serve your bundles
pug-plugin			Renders Pug files to HTML, extracts JS and CSS from sources specified directly in Pug.

Loaders

Webpack enables the use of loaders to preprocess files. This allows you to bundle any static resource way beyond JavaScript. You can easily write your own loaders using Node.js.

Loaders are activated by using loadername! prefixes in require() statements, or are automatically applied via regex from your webpack configuration.

Files

Name	Status	Install Size	Description
val-loader			Executes code as module and considers exports as JS code

JSON

Name	Status	Install Size	Description
			Loads and transpiles a CSON file

Transpiling

Name	Status	Install Size	Description
			Loads ES2015+ code and transpiles to ES5 using Babel
			Loads TypeScript like JavaScript
			Loads CoffeeScript like JavaScript

Templating

Name	Status	Install Size	Description
			Exports HTML as string, requires references to static resources
			Loads Pug templates and returns a function
			Compiles Pug to a function or HTML string, useful for use with Vue, React, Angular
			Compiles Markdown to HTML
			Loads and transforms a HTML file using PostHTML
			Compiles Handlebars to HTML

Styling

Name	Status	Install Size	Description
<style>			Add exports of a module as style to DOM
			Loads CSS file with resolved imports and returns CSS code
			Loads and compiles a LESS file
			Loads and compiles a Sass/SCSS file
			Loads and compiles a Stylus file
			Loads and transforms a CSS/SSS file using PostCSS

Frameworks

Name	Status	Install Size	Description
			Loads and compiles Vue Components
			Process HTML & CSS with preprocessor of choice and require() Web Components like first-class modules
			Loads and compiles Angular 2 Components
			Riot official webpack loader
			Official Svelte loader

Performance

Webpack uses async I/O and has multiple caching levels. This makes webpack fast and incredibly fast on incremental compilations.

Module Formats

Webpack supports ES2015+, CommonJS and AMD modules out of the box. It performs clever static analysis on the AST of your code. It even has an evaluation engine to evaluate simple expressions. This allows you to support most existing libraries out of the box.

Code Splitting

Webpack allows you to split your codebase into multiple chunks. Chunks are loaded asynchronously at runtime. This reduces the initial loading time.

Optimizations

Webpack can do many optimizations to reduce the output size of your JavaScript by deduplicating frequently used modules, minifying, and giving you full control of what is loaded initially and what is loaded at runtime through code splitting. It can also make your code chunks cache friendly by using hashes.

Contributing

We want contributing to webpack to be fun, enjoyable, and educational for anyone, and everyone. We have a vibrant ecosystem that spans beyond this single repo. We welcome you to check out any of the repositories in our organization or webpack-contrib organization which houses all of our loaders and plugins.

Contributions go far beyond pull requests and commits. Although we love giving you the opportunity to put your stamp on webpack, we also are thrilled to receive a variety of other contributions including:

• Documentation updates, enhancements, designs, or bugfixes
• Spelling or grammar fixes
• README.md corrections or redesigns
• Adding unit, or functional tests
• Triaging GitHub issues -- especially determining whether an issue still persists or is reproducible.
• Searching #webpack on twitter and helping someone else who needs help
• Teaching others how to contribute to one of the many webpack's repos!
• Blogging, speaking about, or creating tutorials about one of webpack's many features.
• Helping others in our webpack gitter channel.

To get started have a look at our documentation on contributing.

If you are worried or don't know where to start, you can always reach out to Sean Larkin (@TheLarkInn) on Twitter or simply submit an issue and a maintainer can help give you guidance!

We have also started a series on our Medium Publication called The Contributor's Guide to webpack. We welcome you to read it and post any questions or responses if you still need help.

Looking to speak about webpack? We'd love to review your talk abstract/CFP! You can email it to webpack [at] opencollective [dot] com and we can give pointers or tips!!!

Creating your own plugins and loaders

If you create a loader or plugin, we would <3 for you to open source it, and put it on npm. We follow the x-loader, x-webpack-plugin naming convention.

Support

We consider webpack to be a low-level tool used not only individually but also layered beneath other awesome tools. Because of its flexibility, webpack isn't always the easiest entry-level solution, however we do believe it is the most powerful. That said, we're always looking for ways to improve and simplify the tool without compromising functionality. If you have any ideas on ways to accomplish this, we're all ears!

If you're just getting started, take a look at our new docs and concepts page. This has a high level overview that is great for beginners!!

Looking for webpack 1 docs? Please check out the old wiki, but note that this deprecated version is no longer supported.

If you want to discuss something or just need help, here is our Gitter room where there are always individuals looking to help out!

If you are still having difficulty, we would love for you to post a question to StackOverflow with the webpack tag. It is much easier to answer questions that include your webpack.config.js and relevant files! So if you can provide them, we'd be extremely grateful (and more likely to help you find the answer!)

If you are twitter savvy you can tweet #webpack with your question and someone should be able to reach out and help also.

If you have discovered a 🐜 or have a feature suggestion, feel free to create an issue on GitHub.

License

Core Team

Tobias Koppers Core Founder of webpack

Johannes Ewald Loaders & Plugins Early adopter of webpack

Sean T. Larkin Public Relations Founder of the core team

Kees Kluskens Development Sponsor

Sponsoring

Most of the core team members, webpack contributors and contributors in the ecosystem do this open source work in their free time. If you use webpack for a serious task, and you'd like us to invest more time on it, please donate. This project increases your income/productivity too. It makes development and applications faster and it reduces the required bandwidth.

This is how we use the donations:

• Allow the core team to work on webpack
• Thank contributors if they invested a large amount of time in contributing
• Support projects in the ecosystem that are of great value for users
• Support projects that are voted most (work in progress)
• Infrastructure cost
• Fees for money handling

Premium Partners

Other Backers and Sponsors

Before we started using OpenCollective, donations were made anonymously. Now that we have made the switch, we would like to acknowledge these sponsors (and the ones who continue to donate using OpenCollective). If we've missed someone, please send us a PR, and we'll add you to this list.

Gold Sponsors

Become a gold sponsor and get your logo on our README on GitHub with a link to your site.

Silver Sponsors

Become a silver sponsor and get your logo on our README on GitHub with a link to your site.

Bronze Sponsors

Become a bronze sponsor and get your logo on our README on GitHub with a link to your site.

Backers

Become a backer and get your image on our README on GitHub with a link to your site.

Special Thanks to

(In chronological order)

• @google for Google Web Toolkit (GWT), which aims to compile Java to JavaScript. It features a similar Code Splitting as webpack.
• @medikoo for modules-webmake, which is a similar project. webpack was born because I wanted Code Splitting for modules-webmake. Interestingly the Code Splitting issue is still open (thanks also to @Phoscur for the discussion).
• @substack for browserify, which is a similar project and source for many ideas.
• @jrburke for require.js, which is a similar project and source for many ideas.
• @defunctzombie for the browser-field spec, which makes modules available for node.js, browserify and webpack.
• Every early webpack user, which contributed to webpack by writing issues or PRs. You influenced the direction...
• @shama, @jhnns and @sokra for maintaining this project
• Everyone who has written a loader for webpack. You are the ecosystem...
• Everyone I forgot to mention here, but also influenced webpack.

analyse's Issues

Feature request: Ability to sort assets by size in chunk view

It's currently only possible in the main view

Website not working on Chrome

It shows a blank page. Safari appears to work.

No upload button after selecting file

.jsx files don't show up as files in the module graph

When I put my stats file into webpack.github.io/analyse, all of the modules show up as nodes in the graph except for jsx files, which don't show up at all in the main list of modules. What's confusing is that they do show up as reasons and dependencies when I look at modules that require .jsx files.

Although I am excluding files, the fact that they show up as dependencies seems to indicate that something is else is going on, rather than .jsx files getting excluded. Any thoughts?

Error on analyze

I'm using webpack 2 and when I upload my file, I get an error because my stats.json file doesn't have an assets or chunks property.

There error is here: https://github.com/webpack/analyse/blob/master/app/app.js#L6

Support Webpack v3

The analyse tool is throwing the below error when loading a stats.json file from webpack v3.

web.js:1 Uncaught TypeError: Cannot read property 'sort' of undefined
    at r (web.js:1)
    at Object.e.load (web.js:1)
    at FileReader.e.onload (/analyse/8.568a26e05565c8025a86.js:1)

stats.json

Create repository for dockerfile

Hello,
I want create a dockerfile for analyse app. Can you create repository for it?

Sort by size functionality on #modules, #chunk and #assets

It would be perfect if the table on #modules, #chunk and #assets can be sorted by size.

Hint for circular dependencies

Show hints for circular dependencies...

Errors out, because "Field 'browser' doesn't contain a valid alias configuration"

This seems strange, since the general recommendation nowadays is to move the brrwoserlist configuration to an external .browserlistrc. Which I have.

Or does this error message refer to something other then that?

Is analyse still an active project?

I tried using with a profile file from Webpack v4. After uploading the file nothing happened.

There doesn't seem to be any recent activity, but the package itself doesn't say deprecated or that it is no longer supported. Is analyse still an active project?

Thanks in advance!

Explain the colors meaning

In the Modules tab there are blue and magenta lines connecting green, orange and red dots. What does those colors means? I'm looking for this information and could not find it. Are they part of some standard I'm not aware of, or are they specific to this analyzer and undocumented?

Readme.md - link 404

http://webpack.github.com/analyse should be replaced by https://webpack.github.io/analyse/

Uncaught TypeError: Cannot read property 'sort' of undefined

I am trying to use https://webpack.github.io/analyse/#home but I am getting this:

Uncaught TypeError: Cannot read property 'sort' of undefined
  r @ web.js:1
  t.onload @ 8.970b70af1d8094b96211.js:1

Whether to support Webpack 4.x

i use the packages version is

    "webpack": "^4.15.1",
    "webpack-bundle-analyser": "^1.4.0",
    "webpack-cli": "^3.0.8",
    "webpack-dev-server": "^3.1.4"

is the size of a module shown in the module view its minified/tree-shaken size in the output bundle, or its original source size?

I can't tell.

cannot resolve module `fs` in jade

I am getting the following error when I run grunt, grunt dev or grunt deploy:

ERROR in ./~/jade/lib/runtime.js
Module not found: Error: Cannot resolve module 'fs' in /Users/robertbalicki/Documents/code/analyse/node_modules/jade/lib
 @ ./~/jade/lib/runtime.js 155:12-25

I can fix it (hackily?) by installing browserify-fs as fs in either node_modules or web_modules. It has some unmet peer dependencies, which I haven't dug into.

Please advise - happy to fix this properly, but I haven't grokked the library fully enough to know what direction to go in.

FWIW, setting target: node on the webpack config breaks the require.include(sigma.js) line, but seems to (obviously) fix the fs error.

npm run build failed MainTemplate.getAssetPath is deprecated

$ npm run build

> [email protected] build C:\Users\petovchial\sources\analyse
> rimraf dist && webpack --mode production --env.longTermCaching --env.googleAnalytics

(node:2400) [DEP_WEBPACK_MAIN_TEMPLATE_GET_ASSET_PATH] DeprecationWarning: MainTemplate.getAssetPath is deprecated (use Compilation.getAssetPath instead)
(node:2400) UnhandledPromiseRejectionWarning: ReferenceError: BigInt is not defined
    at compilation.hooks.optimizeChunks.tap.chunks (C:\Users\petovchial\sources\analyse\node_modules\webpack\lib\optimize\SplitChunksPlugin.js:564:19)
    at Hook.eval [as call] (eval at create (C:\Users\petovchial\sources\analyse\node_modules\webpack\node_modules\tapable\lib\HookCodeFactory.js:19:10), <anonymous>:25:16)
    at Hook.CALL_DELEGATE [as _call] (C:\Users\petovchial\sources\analyse\node_modules\webpack\node_modules\tapable\lib\Hook.js:14:14)
    at Compilation.seal (C:\Users\petovchial\sources\analyse\node_modules\webpack\lib\Compilation.js:1643:36)
    at compilation.finish.err (C:\Users\petovchial\sources\analyse\node_modules\webpack\lib\Compiler.js:921:19)
    at hooks.finishModules.callAsync.err (C:\Users\petovchial\sources\analyse\node_modules\webpack\lib\Compilation.js:1546:4)
    at _next1 (eval at create (C:\Users\petovchial\sources\analyse\node_modules\webpack\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:25:1)
    at _err1 (eval at create (C:\Users\petovchial\sources\analyse\node_modules\webpack\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:43:1)
    at asyncLib.each.err (C:\Users\petovchial\sources\analyse\node_modules\webpack\lib\FlagDependencyExportsPlugin.js:249:11)
    at C:\Users\petovchial\sources\analyse\node_modules\neo-async\async.js:2830:7
    at Object.each (C:\Users\petovchial\sources\analyse\node_modules\neo-async\async.js:2850:39)
    at asyncLib.each.err (C:\Users\petovchial\sources\analyse\node_modules\webpack\lib\FlagDependencyExportsPlugin.js:228:18)
    at C:\Users\petovchial\sources\analyse\node_modules\neo-async\async.js:2830:7
    at done (C:\Users\petovchial\sources\analyse\node_modules\neo-async\async.js:2865:11)
    at C:\Users\petovchial\sources\analyse\node_modules\neo-async\async.js:2818:7
    at compilation.cache.get (C:\Users\petovchial\sources\analyse\node_modules\webpack\lib\FlagDependencyExportsPlugin.js:72:11)
    at needCalls (C:\Users\petovchial\sources\analyse\node_modules\webpack\lib\Cache.js:85:6)
    at err (C:\Users\petovchial\sources\analyse\node_modules\webpack\lib\Cache.js:39:11)
    at gotHandlers.push (C:\Users\petovchial\sources\analyse\node_modules\webpack\lib\cache\IdleFileCachePlugin.js:63:8)
    at hooks.get.callAsync (C:\Users\petovchial\sources\analyse\node_modules\webpack\lib\Cache.js:88:6)
    at _promise1.then._result1 (eval at create (C:\Users\petovchial\sources\analyse\node_modules\webpack\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:30:1)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:189:7)
(node:2400) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:2400) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

jQuery not loaded via HTTPS

(You can ignore the Google Analytics error - that's my browser blocking it)

Upgrade Sigma.js to 1.0.3

The included version of Sigma.js causes high CPU usage, whereas the latest version (1.0.3) now uses a different algorithm that doesn't hit the CPU as hard.

nothing happens

When I select file stats.json to upload - nothing happens - firefox, chromium

[feature]Disabling the graphs

Hello,

We forked the repo to disable the graphs: we have a huge number of modules and the graphs crashed the app.

For now, we only commented everything related to graphs

What would be the best way to enable/disable the graphs for the end user ? Ready to submit a PR if needed

Sections other than Modules don't appear to be working

When I upload my stats.json, Modules section works.

Chunks gives me

Uncaught TypeError: Cannot read property 'length' of undefined 3.00b49fb6b59c1a1b6541.js:formatted:1

Hints gives me an empty screen.

I'll happily send my JSON file to your email if you give me one.

hidden modules not working

Document:

https://webpack.js.org/configuration/stats/#statsexcludemodules

Error Anchor:

analyse/app/pages/modules/modules.pug

Line 17 in 9637830

td: pre: code= module.name.split("!").join("\n")

analyse/app/pages/modules/modules.pug

Line 20 in 9637830

each chunk in module.chunks

analyse/app/pages/chunk/chunk.pug

Line 89 in 9637830

td: pre: code= module.name.split("!").join("\n")

analyse/app/pages/chunk/chunk.pug

Line 92 in 9637830

each chunk in module.chunks

Deploy most recent version to website

The deployed version at http://webpack.github.io/analyse/ is older than the code. I know at least it does not pop open a modal for multi-compiles as added in this commit: 20992e5

I can run locally and it works, but it would be better the latest version if it were on the deployed website.

Allow for children builds

We are running into issues as we have seperate builds for client and server. We can do one of two things seperate them completely OR allow the load function in app.js to account for stats.children array. This might take some refactoring BUT with Hacktoberfest coming up might be something worthy of attacking.

for reference our webpack.config.js:

module.exports = exports = [
  require('./configs/webpack/client'),
  require('./configs/webpack/server')
];

This might be a bit more of an enhancement vs. a bug.

"TypeError: t.chunks is undefined" console error when uploading my file

When uploading my stats.json file, I get a TypeError: t.chunks is undefined error.
stats.json.gz

It would actually be a nice addition, to show any error message in the file upload dialog.

Feature request, hide module(and it's depencencies)

I was trying to analyse my project dependency for reusing code in another project which is nearly the same. But found the are over 500 modules, with only 230 of them are belonging to my project. So I think if I can hide modules just by filtering or shortcut, that would be much more helpful.

By now my only solution is for read asset.json as object and filter them by hand and save it again.

Error on stats.json upload

Not sure what the cause is, but when trying to upload stats to the analyse tool, I get this error (Chrome 38.0.2125.111 on OSX 10.10):

The stats file is about ~28.6 MB, so maybe size is an issue?

Cannot read property 'parents' of undefined when opening modules tab

Uncaught TypeError: Cannot read property 'parents' of undefined
    at eval (webpack:///./app/graphs/modules.js?:59)
    at Array.some (<anonymous>)
    at isInChunks (webpack:///./app/graphs/modules.js?:58)
    at eval (webpack:///./app/graphs/modules.js?:61)
    at Array.some (<anonymous>)
    at eval (webpack:///./app/graphs/modules.js?:50)
    at Array.forEach (<anonymous>)
    at eval (webpack:///./app/graphs/modules.js?:45)
    at Array.forEach (<anonymous>)
    at eval (webpack:///./app/graphs/modules.js?:19)

Analysis web page crashes on Hints

Bug report

Regarding http://webpack.github.io/analyse/#hints

What is the current behavior?
If you go to "Hints" tab in the analysis page, it crashes, and must be reloaded in order to work again.
http://webpack.github.io/analyse/#hints

If the current behavior is a bug, please provide the steps to reproduce.
Upload a stats.json file on http://webpack.github.io/analyse/ and click the tab Hints. After that the page becomes unresponsive. Not sure if this happens for any stats.json, but I can not currently attach the offending one to this ticket. This error can be seen in developer console at the moment you click Hints:

15f6448ec2a08f35395d.js:1 [Violation] 'load' handler took 463ms
f82681492bc705423f7a.js:1 Uncaught (in promise) TypeError: Cannot read property 'join' of undefined
    at f82681492bc705423f7a.js:1
    at f82681492bc705423f7a.js:1
    at e.exports (f82681492bc705423f7a.js:1)
    at e.exports (f82681492bc705423f7a.js:1)
    at HTMLDocument.<anonymous> (web.js:1)
    at j (jquery-2.1.0.min.js:2)
    at Object.add [as done] (jquery-2.1.0.min.js:2)
    at o.fn.init.o.fn.ready (jquery-2.1.0.min.js:2)
    at new o.fn.init (jquery-2.1.0.min.js:2)
    at o (jquery-2.1.0.min.js:2)
(anonymous) @ f82681492bc705423f7a.js:1
(anonymous) @ f82681492bc705423f7a.js:1
e.exports @ f82681492bc705423f7a.js:1
e.exports @ f82681492bc705423f7a.js:1
(anonymous) @ web.js:1
j @ jquery-2.1.0.min.js:2
add @ jquery-2.1.0.min.js:2
o.fn.ready @ jquery-2.1.0.min.js:2
o.fn.init @ jquery-2.1.0.min.js:2
o @ jquery-2.1.0.min.js:2
i @ web.js:1
Promise.then (async)
i @ web.js:1
a @ web.js:1
(anonymous) @ web.js:1

What is the expected behavior?
To get some hints or a message saying there are no hints. No uncaught errors in console.

Other relevant information:
webpack version: "webpack": "^4.44.1",
Node.js version: v14.8.0
Operating System: Mac OS 10.12.6
Additional tools: "stats-webpack-plugin": "^0.7.0",

---

This issue was moved from webpack/webpack#11711 by @evilebottnawi. Original issue was by @perqa.

Error running production build. Fresh install.

Fresh install. Ran default "grunt" task for the first time. Got the following.

Running "copy:main" (copy) task
Copied 1 files

Running "webpack:production" (webpack) task
Version: webpack 1.12.12
                     Asset     Size  Chunks             Chunk Names
 6.c409385e8da907ce65d1.js  12.1 kB       6  [emitted]
                    web.js   102 kB       0  [emitted]  main
 2.c409385e8da907ce65d1.js  3.94 kB       2  [emitted]
 3.c409385e8da907ce65d1.js   5.6 kB       3  [emitted]
 4.c409385e8da907ce65d1.js  4.91 kB       4  [emitted]
 5.c409385e8da907ce65d1.js  11.5 kB       5  [emitted]
 1.c409385e8da907ce65d1.js  9.06 kB       1  [emitted]
 7.c409385e8da907ce65d1.js  1.35 kB       7  [emitted]
 8.c409385e8da907ce65d1.js  1.97 kB       8  [emitted]
 9.c409385e8da907ce65d1.js  2.61 kB       9  [emitted]
10.c409385e8da907ce65d1.js  1.33 kB      10  [emitted]
11.c409385e8da907ce65d1.js   869 kB      11  [emitted]

WARNING in web.js from UglifyJs
Dropping side-effect-free statement [./app/entry.js:54,0]
Dropping side-effect-free statement [./app/entry.js:55,0]
Dropping side-effect-free statement [./app/entry.js:56,0]
Dropping side-effect-free statement [./app/entry.js:57,0]
Side effects in initialization of unused variable findById [./app/graphs/modules.js:3,0]
Side effects in initialization of unused variable chunkCount [./app/graphs/modules.js:12,0]
Condition always true [./app/googleAnalytics.js:1,0]
Dropping unreachable code [./app/googleAnalytics.js:30,0]

WARNING in 1.c409385e8da907ce65d1.js from UglifyJs
Dropping unused variable interp [./~/jade-loader!./app/pages/module/module.jade:8,0]

WARNING in 2.c409385e8da907ce65d1.js from UglifyJs
Dropping unused variable interp [./~/jade-loader!./app/pages/assets/assets.jade:8,0]

WARNING in 3.c409385e8da907ce65d1.js from UglifyJs
Side effects in initialization of unused variable findById [./app/graphs/chunks.js:3,0]
Dropping unused variable interp [./~/jade-loader!./app/pages/chunks/chunks.jade:8,0]

WARNING in 4.c409385e8da907ce65d1.js from UglifyJs
Dropping unused variable interp [./~/jade-loader!./app/pages/modules/modules.jade:8,0]

WARNING in 5.c409385e8da907ce65d1.js from UglifyJs
Dropping unused variable interp [./~/jade-loader!./app/pages/hints/hints.jade:8,0]

WARNING in 6.c409385e8da907ce65d1.js from UglifyJs
Dropping unused variable interp [./~/jade-loader!./app/pages/chunk/chunk.jade:8,0]

WARNING in 7.c409385e8da907ce65d1.js from UglifyJs
Dropping unused variable interp [./~/jade-loader!./app/pages/warnings/warnings.jade:8,0]

WARNING in 8.c409385e8da907ce65d1.js from UglifyJs
Dropping unused variable interp [./~/jade-loader!./app/pages/upload/application.jade:8,0]

WARNING in 9.c409385e8da907ce65d1.js from UglifyJs
Dropping unused variable interp [./~/jade-loader!./app/pages/home/home.jade:8,0]

WARNING in 10.c409385e8da907ce65d1.js from UglifyJs
Dropping unused variable interp [./~/jade-loader!./app/pages/errors/errors.jade:8,0]

ERROR in ./~/jade/lib/runtime.js
Module not found: Error: Cannot resolve module 'fs' in /Users/matt/Sites/webpack-analyse/node_modules/jade/lib
 @ ./~/jade/lib/runtime.js 155:12-25
Warning: Task "webpack:production" failed. Use --force to continue.

Aborted due to warnings.

Here's some info on my environment

OSX El Capitan v10.11.13
npm: v3.5.3
node: v5.0.0
grunt-cli: v0.1.13
grunt: v0.4.5