fix(template): the generated app could not be built at all

[rubenvdlinde]

Fixes #38.

A wizard-generated app failed npm run build out of the box, so every repo OpenBuild published was uninstallable. Three separate causes, each found and verified by running a real build of the emitted 72-file scaffold.

1. terser-webpack-plugin was declared by nobody

[webpack-cli] Error: Cannot find module 'terser-webpack-plugin'
  requireStack: [ node_modules/@nextcloud/webpack-vue-config/webpack.config.js, … ]

@nextcloud/webpack-vue-config requires it but neither depends on it nor lists it as a peer (its peers are @babel/core, babel-loader, css-loader, node-polyfill-webpack-plugin, sass, sass-loader, style-loader, ts-loader). Nothing installed it, so webpack could not start.

2. @nextcloud/axios@2.6.0 dropped its require export — in a minor bump

@nextcloud/axios 2.5.2  exports {".": {types, import, require: "./dist/index.cjs"}}   ✅
@nextcloud/axios 2.6.0  exports {".": {types, import}}          — ESM only            ❌

@nextcloud/vue's CJS build require()s it, so the caret range ^2.5.0 floated into an unusable pair and webpack emitted 14 errors:

ERROR in ./node_modules/@nextcloud/vue/dist/index.cjs 85:0-27
Module not found: "." is not exported under the conditions
["require","module-sync","module","webpack","production","browser"] from @nextcloud/axios

Pinning the direct dependency is not enough — npm nests its own copy under @nextcloud/vue, and that is the copy that breaks:

before override:  @nextcloud/axios -> 2.5.2 ✅
                  @nextcloud/vue/node_modules/@nextcloud/axios -> 2.6.0 ❌   <-- the one that fails
after override:   @nextcloud/axios -> 2.5.2   (single copy, all nesting collapsed)

So this needs an overrides entry, which applies transitively.

3. Node's path was left unpolyfilled

@conduction/nextcloud-vue bundles a @nextcloud/dialogs chunk that reaches for Node's path. Webpack 5 stopped auto-polyfilling core modules, so the browser build could not resolve it.

Mapped just path to path-browserify rather than adding a blanket node-polyfill plugin — it is the only core module the dependency actually touches, and a blanket polyfill would grow every generated app's bundle for nothing.

Verification

Ran the emitted scaffold through a real npm install + npm run build after each fix:

	errors
as shipped	build cannot start (missing terser)
+ terser	14
+ axios override	1
+ path fallback	0 — real bundles produced

Only the pre-existing entrypoint-size warnings remain.

Suggested follow-up

A CI guard that generates an app and runs npm ci && npm run build. All three defects are invisible to any test that stops at "the files were generated", which is why a scaffold that never built shipped.

Related: #35 — push fails with a misleading github_unreachable; the real cause there is GitHub rejecting the tree because the scaffold ships 9 .github/workflows/* files and the brokered token lacks the workflow permission.