otakustay posted a new feature request
webpackbar •
I used webpackbar with webpack 5 for a while and found no compatibility issue, since npm 7 requires peer dependencies to match strictly, it is better to publish a new version upgrading peerDependencies to enable webpack 5
Flcwl posted a new feature request
webpackbar •
Can't see the full error message when building My App. It would be a problem if error when building, I can't troubleshoot errors quickly maybe running webpack compiler in CI or Docker.
Now It is pretty good and useful for me, But I really hope it can show the full error when an error occurs in the future, It will be better.
windyrain posted a new question
webpackbar •
when I use webpackbar,I can't see babel-plugin-react-css-modules warning log.
https://github.com/gajus/babel-plugin-react-css-modules/blob/master/src/getClassName.js#L20
how can I see the warning with webpackbar
OliverJAsh posted a new bug report
webpackbar •
https://github.com/OliverJAsh/webpack-concurrently/tree/bar
Reduced test case: https://github.com/OliverJAsh/webpack-concurrently/tree/bar
Note: you must use the bar
branch.
Run yarn
and then npm run compile
.
We are running two webpack builds concurrently. Each webpack build has its own instance of the WebpackBar
plugin, with a unique name
(client
and server
).
client
and server
.I would not expect this flickering—each build should have its own bar and it should not interfere with other bar instances.
atilkan posted a new bug report
webpackbar •
My version is 4. It is not listed in options. I am on windows and i setup as poor ass docs says. Nothing show on console.
It doesn't show "fancy" bars.
Says compiling and done as Basic mode.
atilkan posted a new question
webpackbar •
It is not mentioned that this plugin is not printing or showing bars with the --hide-modules option.
yezishan posted a new question
webpackbar •
"webpackbar": 4.0.0
just as show in the pic, the result of stats has no content ?
hrodriguez758 posted a new question
webpackbar •
This is the current output
application: ✔ Webpack
application: Compiled successfully in 1.93s
lerna success run Ran npm script 'build:release' in 1 package in 6.1s:
lerna success - application
✨ Done in 6.93s.
and should be
$ yarn build
yarn run v1.17.3
$ yarn build:release
$ lerna run build:release --stream
lerna notice cli v3.16.4
lerna info Executing command in 1 package: "yarn run build:release"
application: $ yarn build:release:application && yarn build:release:renderer
application: $ webpack --color --mode production --config webpack.main.config.js
✔ Webpack
application: Compiled successfully in 1.47s
application: $ webpack --color --mode production --config webpack.renderer.config.js
✔ Webpack
application: Compiled successfully in 1.91s
lerna success run Ran npm script 'build:release' in 1 package in 6.1s:
lerna success - application
✨ Done in 6.98s.
Basically the method _renderStates in the FancyReporter class is adding unnecessaries jump lines ("\n")
_renderStates(statesArray) {
lastRender = Date.now();
const renderedStates = statesArray.map(c => this._renderState(c)).join('\n\n');
logUpdate.render("\n" + renderedStates + "\n");
}
The fix for this issue is just to remove the unnecessaries jump lines like this:
_renderStates(statesArray) {
lastRender = Date.now();
const renderedStates = statesArray.map(c => this._renderState(c)).join('\n');
logUpdate.render(renderedStates);
}
hrodriguez758 posted a new bug report
webpackbar •
Run with the reporter option in fancy
The output should be
$ yarn build
yarn run v1.17.3
$ yarn build:release
$ lerna run build:release --stream
lerna notice cli v3.16.4
lerna info Executing command in 1 package: "yarn run build:release"
application: $ yarn build:release:application && yarn build:release:renderer
application: $ webpack --color --mode production --config webpack.main.config.js
✔ Webpack
application: Compiled successfully in 1.47s
application: $ webpack --color --mode production --config webpack.renderer.config.js
✔ Webpack
application: Compiled successfully in 1.91s
lerna success run Ran npm script 'build:release' in 1 package in 6.1s:
lerna success - application
✨ Done in 6.98s.
The current output is
application: ✔ Webpack
application: Compiled successfully in 1.93s
lerna success run Ran npm script 'build:release' in 1 package in 6.1s:
lerna success - application
✨ Done in 6.93s.
Basically the method _renderStates in the FancyReporter class is adding unnecessaries jump lines ("\n")
_renderStates(statesArray) {
lastRender = Date.now();
const renderedStates = statesArray.map(c => this._renderState(c)).join('\n\n');
logUpdate.render("\n" + renderedStates + "\n");
}
The fix for this issue is just to remove the unnecessaries jump lines like this:
_renderStates(statesArray) {
lastRender = Date.now();
const renderedStates = statesArray.map(c => this._renderState(c)).join('\n');
logUpdate.render(renderedStates);
}
hrodriguez758 posted a new question
webpackbar •
This is the current output
application: ✔ Webpack
application: Compiled successfully in 1.93s
lerna success run Ran npm script 'build:release' in 1 package in 6.1s:
lerna success - application
✨ Done in 6.93s.
and should be
$ yarn build
yarn run v1.17.3
$ yarn build:release
$ lerna run build:release --stream
lerna notice cli v3.16.4
lerna info Executing command in 1 package: "yarn run build:release"
application: $ yarn build:release:application && yarn build:release:renderer
application: $ webpack --color --mode production --config webpack.main.config.js
✔ Webpack
application: Compiled successfully in 1.47s
application: $ webpack --color --mode production --config webpack.renderer.config.js
✔ Webpack
application: Compiled successfully in 1.91s
lerna success run Ran npm script 'build:release' in 1 package in 6.1s:
lerna success - application
✨ Done in 6.98s.
Basically the method _renderStates
in the FancyReporter class is adding unnecessaries jump lines ("\n")
_renderStates(statesArray) {
lastRender = Date.now();
const renderedStates = statesArray.map(c => this._renderState(c)).join('\n\n');
logUpdate.render("\n" + renderedStates + "\n");
}
The fix for this issue is just to remove the unnecessaries jump lines like this:
_renderStates(statesArray) {
lastRender = Date.now();
const renderedStates = statesArray.map(c => this._renderState(c)).join('\n');
logUpdate.render(renderedStates);
}
Tom910 posted a new feature request
webpackbar •
Currently, webpackbar don't show all the information about the build. For example
This wepbackBar:
● Server █████████████████████████ basic chunk optimization (76%)
This ProfilePlugin at the same time:
77% advanced chunk optimization LimitChunkCountPlugin
In this case, I spend more time in the search were a problem in build. Because additional information was skipped
Show additional information about plugins
● Server █████████████████████████ basic chunk optimization (76%)
LimitChunkCountPlugin
yuchonghua posted a new question
webpackbar •
Looking forward to a support for index.d.ts, because it is inconvenient to use without TypeScript
yuchonghua posted a new question
webpackbar •
Looking forward to a support for index.d.ts, because it is inconvenient to use without TypeScript
dima74 posted a new question
webpackbar •
Please consider casting path
in this line to string:
Because in my experience path
can be number.
I don't have any good reproduction (sorry), so my proposal is to just add cast to string. Just to be complete, here is full stack trace with this error:
PATH/node_modules/@nuxt/webpack/node_modules/webpackbar/dist/utils/index.js:58
return path.replace(cwd, '');
^
TypeError: path.replace is not a function
at shortenPath (PATH/node_modules/@nuxt/webpack/node_modules/webpackbar/dist/utils/index.js:58:15)
at PATH/node_modules/@nuxt/webpack/node_modules/webpackbar/dist/plugin.js:182:43
at SyncHook.eval [as call] (eval at create (PATH/node_modules/@nuxt/webpack/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:19:10), <anonymous>:7:1)
at SyncHook.lazyCompileHook (PATH/node_modules/@nuxt/webpack/node_modules/webpack/node_modules/tapable/lib/Hook.js:154:20)
at Watchpack.watcher.compiler.watchFileSystem.watch (PATH/node_modules/@nuxt/webpack/node_modules/webpack/lib/Watching.js:139:33)
at Object.onceWrapper (events.js:285:13)
at Watchpack.emit (events.js:197:13)
at Watchpack.EventEmitter.emit (domain.js:446:20)
at Watchpack._onChange (PATH/node_modules/watchpack/lib/watchpack.js:118:7)
at Watchpack.<anonymous> (PATH/node_modules/watchpack/lib/watchpack.js:109:8)
at Watcher.emit (events.js:197:13)
at Watcher.EventEmitter.emit (domain.js:446:20)
at PATH/node_modules/watchpack/lib/DirectoryWatcher.js:101:9
at Array.forEach (<anonymous>)
at DirectoryWatcher.setFileTime (PATH/node_modules/watchpack/lib/DirectoryWatcher.js:99:42)
at DirectoryWatcher.onFileAdded (PATH/node_modules/watchpack/lib/DirectoryWatcher.js:250:7)
at FSWatcher.emit (events.js:197:13)
at FSWatcher.EventEmitter.emit (domain.js:446:20)
at FSWatcher.<anonymous> (PATH/node_modules/watchpack/node_modules/chokidar/index.js:199:15)
at FSWatcher._emit (PATH/node_modules/watchpack/node_modules/chokidar/index.js:241:5)
at FSWatcher.<anonymous> (PATH/node_modules/watchpack/node_modules/chokidar/lib/nodefs-handler.js:465:12)
at FSReqCallback.oncomplete (fs.js:159:5)
shahzaibkhalid posted a new question
webpackbar •
First of all, thanks so much for this wonderful progress bar.
I was using webpackbar and tried to write a stats.json
file to be used by webpack-bundle-analyzer
.
Here's my npm script:
webpack --env=production --profile --json > stats.json
However, stats.json contains some output from webpackbar. Here's how it looks like:
ℹ Compiling Webpack webpackbar 18:06:57
✔ Webpack: Compiled successfully in 3.22s webpackbar 18:07:00
{
"errors": [],
"warnings": [],
"version": "4.29.3",
"hash": "ed64caf72379ba267639",
"time": 3228,
"builtAt": 1549976820840,
"publicPath": "/",
"outputPath": "/Users/shahzaib/my-stuff/serious-projects/testing-shaizei/copy-jetsetter/build",
"assetsByChunkName": {
"main": [
// remaining file is not included for brevity
}
Due to these two lines (in the start), stats.json
is becoming invalid.
Any workaround for this?
jimblue posted a new feature request
webpackbar •
As Webpackbar, some other Webpack plugins also show compilation time.
Obviously this information is not needed twice, so it could be nice to be able hide hide it.
Thanks
mohsinulhaq posted a new question
webpackbar •
ERROR [karma]: TypeError: this.__write is not a function
at WriteStream.write (node_modules/webpackbar/dist/utils/log-update.js:89:16)
at adapters.forEach (node_modules/karma/lib/reporters/base.js:73:16)
at Array.forEach (<anonymous>)
at MochaReporter.BaseReporter.write (node_modules/karma/lib/reporters/base.js:68:19)
at MochaReporter.BaseReporter.writeCommonMsg (node_modules/karma/lib/reporters/base.js:79:16)
at MochaReporter.BaseReporter.onBrowserLog (node_modules/karma/lib/reporters/base.js:100:12)
at Server.<anonymous> (node_modules/karma/lib/events.js:40:26)
at Server.emit (events.js:187:15)
at Browser.onInfo (node_modules/karma/lib/browser.js:100:20)
at Socket.socket.on (node_modules/karma/lib/browser.js:272:38)
It seems that your reporter is clashing with Karma's reporter when overriding process.stdout.write
. Am I doing something wrong or is this a known issue?
zombieJ posted a new question
webpackbar •
3.1.3
https://github.com/nuxt/webpackbar
update webpack to 4.
(Seems webpack 4 updated the plugin interface.)
No warning log
(node:89719) DeprecationWarning: Tapable.plugin is deprecated. Use new API on `.hooks` instead
at WebpackBarPlugin.apply (/projects/antd/rc-antd/node_modules/[email protected]3.12.0@webpack/lib/ProgressPlugin.js:59:13)
at WebpackBarPlugin.apply (/projects/antd/rc-antd/node_modules/[email protected]3.1.3@webpackbar/dist/plugin.js:158:11)
at webpack (/projects/antd/rc-antd/node_modules/[email protected]4.27.1@webpack/lib/webpack.js:47:13)
at options.map.options (/projects/antd/rc-antd/node_modules/[email protected]4.27.1@webpack/lib/webpack.js:35:55)
at Array.map (<anonymous>)
at webpack (/projects/antd/rc-antd/node_modules/[email protected]4.27.1@webpack/lib/webpack.js:35:40)
at dist (/projects/antd/rc-antd/node_modules/[email protected]6.1.0@antd-tools/lib/gulpfile.js:40:3)
at Gulp.gulp.task.done (/projects/antd/rc-antd/node_modules/[email protected]6.1.0@antd-tools/lib/gulpfile.js:102:3)
at module.exports (/projects/antd/rc-antd/node_modules/_orchestrator@[email protected]orchestrator/lib/runTask.js:34:7)
at Gulp.Orchestrator._runTask (/projects/antd/rc-antd/node_modules/[email protected]0.3.8@orchestrator/index.js:273:3)
at Gulp.Orchestrator._runStep (/projects/antd/rc-antd/node_modules/[email protected]0.3.8@orchestrator/index.js:214:10)
at Gulp.Orchestrator.start (/projects/antd/rc-antd/node_modules/[email protected]0.3.8@orchestrator/index.js:134:8)
at Object.<anonymous> (/projects/antd/rc-antd/node_modules/[email protected]6.1.0@antd-tools/lib/cli/run.js:25:8)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
alerg posted a new question
webpackbar •
"next": "7.0.2"
----"webpack": "4.20.2"
--------"webpackbar": "2.6.3"
------------"table": "4.0.3"
The dependency "table" that has "webpackbar" installs dependencies with the prefix ^. One of its dependencies removed code that caused the next build process to be broken:
Error: Cannot find module 'ajv/lib/compile/equal'
at Function.Module.resolveFilename (module.js:547:15)
at Function.Module.load (module.js:474:25)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/nodemodules/table/dist/validateConfig.js:2:13)
at Module.compile (module.js:652:30)
at Object.Module.extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module.load (module.js:497:3)