Skip to content
This repository has been archived by the owner on Jun 10, 2023. It is now read-only.

Update webpack-dashboard to the latest version 🚀 #282

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

greenkeeper[bot]
Copy link

@greenkeeper greenkeeper bot commented May 24, 2018

Version 2.0.0 of webpack-dashboard was just published.

Dependency webpack-dashboard
Current Version 1.1.1
Type devDependency

The version 2.0.0 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of webpack-dashboard.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.


Release Notes 2.0.0

This is a major update to webpack-dashboard with breaking changes. And a lot of speed and coolness.

Breaking changes

  • Requires node6+.
  • Use the webpack internal stats object instead of real bundles. This is faster and with less futzing / parsing on the dashboard's end. Should permanently fix the no code sections found errors.
  • We've removed command flags / plugin options that no longer apply like --root, etc.

Modules

  • Removed min and min+gz estimated file sizes from modules outputs. This dramatically speeds up the dashboard and reduces CPU usage.

Versions

  • Version skews should be detected more accurately and much faster thanks to dramatically improved heuristics from inspectpack.

Duplicates

  • Duplicates now reports on duplicate files that are (1) completely identical, and (2) the same package name and file path but with different sources. The first are low hanging fruit for optimizations in your build -- you've literally got the same thing multiple times. The latter needs to be coalesced at the package dependency level -- something the versions output can help with.

Issues

  • Upgrade hooks to work in webpack1-4 with abstraction. Fixes #240

Refactoring

  • Switch from chalk to using Blessed's built-in tags for coloring. This is definitely the way to go as things like table spacing don't work with chalk strings and work like a charm with Blessed tags.
  • Update dependencies and remove lots of unused things (like lodash, chalk, bluebird and a whole lot of babel* that apparently wasn't used anyways).
    • New inspectpack is way slimmer and faster, with no more binary dependencies!
  • Switch to yarn-only workflow in dev.
  • Bump Travis node versions.
Commits

The new version differs by 2 commits.

  • 5b65faa 2.0.0
  • 8a32cd1 [Major] Integrate inspectpack3 - faster, better, and more colorful! (#249)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper bot 🌴

@codecov-io
Copy link

Codecov Report

Merging #282 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #282   +/-   ##
=======================================
  Coverage   95.75%   95.75%           
=======================================
  Files          25       25           
  Lines         165      165           
  Branches       10       10           
=======================================
  Hits          158      158           
  Misses          6        6           
  Partials        1        1

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bf4795c...731c729. Read the comment docs.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant