sfcode
An Online Competing and Development Environment
|
The first step to optimising your webpack build speed, is to know where to focus your attention.
This plugin measures your webpack build speed, giving an output like this:
or
SMP requires at least Node v6. But otherwise, accepts all webpack versions (1, 2, 3, and 4).
Change your webpack config from
to
and you're done! SMP will now be printing timing output to the console by default.
Check out the examples folder for some more examples.
Pass these into the constructor, as an object:
Type: Boolean
Default: false
If truthy, this plugin does nothing at all.
{ disable: !process.env.MEASURE }
allows opt-in measurements with MEASURE=true npm run build
.
Type: String|Function
Default: "human"
Determines in what format this plugin prints its measurements
"json"
- produces a JSON blob"human"
- produces a human readable output"humanVerbose"
- produces a more verbose version of the human readable outputType: String|Function
Default: console.log
Type: Object
Default: {}
By default, SMP derives plugin names through plugin.constructor.name
. For some plugins this doesn't work (or you may want to override this default). This option takes an object of pluginName: PluginConstructor
, e.g.
Type: Boolean
Default: false
By default, SMP measures loaders in groups. If truthy, this plugin will give per-loader timing information.
This flag is experimental. Some loaders will have inaccurate results:
thread-loader
)file-loader
)We will find solutions to these issues before removing the _(experimental)_ flag on this option.
This tends to be down to webpack reading in from the file-system, but in general it's anything outside of what SMP can actually measure.
It means vanilla JS files, which webpack can handle out of the box.
Contributors are welcome! 😊
Please check out the CONTRIBUTING.md.
SMP follows semver. If upgrading a major version, you can consult the migration guide.