pg-manual: webpack mode hardcoded to 'development' — npm run build produces dev bundle

[dobby-coder]

Problem

pg-manual/webpack.config.js:7 hardcodes:

const webpackMode = 'development'

mode is passed directly to webpack with no override path, so npm run build always produces a development bundle:

• No minification
• Cheap source maps embedded
• process.env.NODE_ENV not set to 'production' for libraries that branch on it

There is no way to produce a production build of pg-manual today.

Suggested fix

Honour NODE_ENV (and/or webpack's --mode CLI flag) so npm run build defaults to production while npm run dev (webpack-dev-server) stays on development.

One small change:

const webpackMode = process.env.NODE_ENV === 'development' ? 'development' : 'production'

…and let webpack-dev-server set NODE_ENV=development itself (it does by default), or invoke it as cross-env NODE_ENV=development webpack serve in the dev script. Alternatively pass --mode from each npm script and remove the mode field entirely.

Verify with the existing dep-bump build check (pg-manual: npm install && npm run build must compile cleanly with zero export … was not found warnings) — see the build-and-bump-gotchas note.

Files

• pg-manual/webpack.config.js:7 — the hardcoded constant
• pg-manual/package.json — build / dev npm scripts may also need tweaking depending on which approach is taken

Scope

pg-manual only. pg-sveltekit's Vite build and pg-node's Node script are unaffected.

[dobby-coder]

/dobby

[dobby-coder]

Dobby has received the request! Routing to the right specialist now...

[dobby-coder]

Plan

Pass --mode from each npm script and drop the hardcoded mode field from the config (the second option from the issue body — simplest, no cross-env dependency, unambiguous).

Changes

pg-manual/webpack.config.js

• Delete const webpackMode = 'development' (line 7).
• Delete mode: webpackMode, (line 11). Webpack reads --mode from the CLI instead.

pg-manual/package.json

• build: webpack → webpack --mode production
• dev: npx webpack serve → webpack serve --mode development

Verification

• cd pg-manual && npm install && npm run build — must compile cleanly, with zero export ... was not found warnings (per build-and-bump-gotchas note), and produce a minified dist/ bundle.
• Confirm dist/*.js is minified (production output, not dev).
• npm run dev not run end-to-end here (would need to bind to a port and click through Yivi), but the --mode development flag is equivalent to the previous hardcoded value, so behaviour matches.

Scope

pg-manual only. pg-sveltekit and pg-dotnet unaffected. No README change — the existing instructions still apply.

Delivery

One PR, ready-for-review (this repo has no CI workflow, so a draft would sit invisible), assigned to @rubenhensen, with Closes #51. Title: fix(pg-manual): respect --mode so npm run build produces a production bundle.

[rubenhensen]

/dobby this is an example app and does not need a production version

[dobby-coder]

Dobby has received the request! Routing to the right specialist now...

[dobby-coder]

Understood — standing down. PR #56 is closed and this agent has saved a note so future routine triage scans treat the dev-mode webpack config in pg-manual as intentional and won't refile.