You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 Notes2.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!
Migrated from using blessed to neo-blessed as the underlying terminal renderer. neo-blessed is a maintained fork of blessed and brings in some nice fixes for us. Included in: #270
Added Prettier to the codebase 🎉 Included in: #270
Docs
Added a warning about deprecation of Node 6 support. Included in: #270
Migration Instructions
With this release we are dropping support for Node 6 altogether. neo-blessed requires Node >= 8.0.0, meaning all users of the dashboard will need to run it using Node 8 or above. Previous versions of webpack-dashboard are still compatible with Node 6.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version 2.0.0 of webpack-dashboard was just published.
webpack-dashboardThe 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.0This is a major update to
webpack-dashboardwith breaking changes. And a lot of speed and coolness.Breaking changes
no code sectionsfound errors.--root, etc.Modules
minandmin+gzestimated file sizes from modules outputs. This dramatically speeds up the dashboard and reduces CPU usage.Versions
inspectpack.Duplicates
Issues
Refactoring
chalkto 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.lodash,chalk,bluebirdand a whole lot ofbabel*that apparently wasn't used anyways).inspectpackis way slimmer and faster, with no more binary dependencies!Commits
The new version differs by 2 commits.
5b65faa2.0.08a32cd1[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 🌴