oppi.li / perf-test
loading up the forgejo repo on tangled to test page performance
0
fork

Configure Feed

Select the types of activity you want to include in your feed.

chore: always enable webpack progress (#7463)

- Webpack is currently quite slow while compiling the whole frontend, even for a very fast machine this can take 30s, but for normal machines this can take over a minute. In the development mode (`make watch`) a handy status is shown that tells what webpack is doing and an approximate progress.
- Enable this progress always, this means that this is now also shown when you run `make build` and should hopefully give a good indication how long the webpack step should take.
- Configure the progress to also show the module its currently 'working on'. This is more interesting than the amount of modules webpack still needs to work on (which steadily increase as webpack seems to incrementally resolves to more modules).

## Screenshot

![image](/attachments/96b1176a-6a6b-4a44-a8f3-fb56ce7b0fc6)

Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/7463
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: Gusted <postmaster@gusted.xyz>
Co-committed-by: Gusted <postmaster@gusted.xyz>

authored by

Gusted
Gusted and committed by
Gusted 56cc841b 2e6f624d

+4 -1
+4 -1
webpack.config.js
··· 16 16 import postcssNesting from 'postcss-nesting'; 17 17 18 18 const {EsbuildPlugin} = EsBuildLoader; 19 - const {SourceMapDevToolPlugin, DefinePlugin} = webpack; 19 + const {SourceMapDevToolPlugin, DefinePlugin, ProgressPlugin} = webpack; 20 20 const formatLicenseText = (licenseText) => wrapAnsi(licenseText || '', 80).trim(); 21 21 22 22 const baseDirectory = dirname(fileURLToPath(new URL(import.meta.url))); ··· 233 233 ], 234 234 }, 235 235 plugins: [ 236 + new ProgressPlugin({ 237 + activeModules: true, 238 + }), 236 239 new webpack.ProvidePlugin({ // for htmx extensions 237 240 htmx: 'htmx.org', 238 241 }),