Bumps [fast-uri](https://github.com/fastify/fast-uri) from 3.1.4 to 3.1.5.
- [Release notes](https://github.com/fastify/fast-uri/releases)
- [Commits](fastify/fast-uri@v3.1.4...v3.1.5)

---
updated-dependencies:
- dependency-name: fast-uri
  dependency-version: 3.1.5
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [postcss](https://github.com/postcss/postcss) from 8.5.22 to 8.5.25.
- [Release notes](https://github.com/postcss/postcss/releases)
- [Changelog](https://github.com/postcss/postcss/blob/main/CHANGELOG.md)
- [Commits](postcss/postcss@8.5.22...8.5.25)

---
updated-dependencies:
- dependency-name: postcss
  dependency-version: 8.5.25
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps the dependencies group with 1 update: [pnpm/action-setup](https://github.com/pnpm/action-setup).


Updates `pnpm/action-setup` from 6.0.9 to 6.0.10
- [Release notes](https://github.com/pnpm/action-setup/releases)
- [Commits](pnpm/action-setup@0ebf471...0977fd9)

---
updated-dependencies:
- dependency-name: pnpm/action-setup
  dependency-version: 6.0.10
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

…on (#4828)

* chore(ci): add gitignore case

* ci(codecov): fix wrong settings

Bumps the dependencies group with 1 update: [changesets/action](https://github.com/changesets/action).


Updates `changesets/action` from 1.9.0 to 2.0.0
- [Release notes](https://github.com/changesets/action/releases)
- [Changelog](https://github.com/changesets/action/blob/main/CHANGELOG.md)
- [Commits](changesets/action@a45c4d5...22ccf9a)

---
updated-dependencies:
- dependency-name: changesets/action
  dependency-version: 2.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps the dependencies group with 1 update: [changesets/action](https://github.com/changesets/action).


Updates `changesets/action` from 2.0.0 to 2.1.0
- [Release notes](https://github.com/changesets/action/releases)
- [Changelog](https://github.com/changesets/action/blob/main/CHANGELOG.md)
- [Commits](changesets/action@22ccf9a...198f833)

---
updated-dependencies:
- dependency-name: changesets/action
  dependency-version: 2.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* ci: node 26

* test: dont use experimental-transform-types on v26

* test: fix failing tests

* chore: revert flag append

* test: use new loader api and fallback to old

* ci: add node 25 to test matrix

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

---------

Co-authored-by: Even Stensberg <evenstensberg@gmail.com>
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

)

Bump the dev dependency to `webpack-dev-server@6` and add snapshots for it,
which the snapshot resolver already supports through the
`.snap.devServer<major>.webpack<major>` extension. CI now runs the test matrix
against both v5 and v6, installing v5 with npm for that job.

`webpack-dev-server` v6 is ESM and exposes the server as its `default` export,
while v5 exports it directly, so the CLI now resolves the constructor type from
the default export when there is one. Runtime behavior is unchanged, the package
was already loaded through `(await import(pkg)).default`.

…n init templates (#4833)

Replace css-loader, style-loader, vue-style-loader and mini-css-extract-plugin
with `experiments.css`, and html-webpack-plugin and html-loader with
`experiments.html`, where `index.html` becomes the entry point.

Both experiments default to "auto" since webpack 5.109, so the templates only
declare them when the auto detection would turn them off: a PostCSS rule for
`.css` files, and the Vue template, where VueLoaderPlugin clones every non-vue
rule with a catch-all `resource: () => true` matcher before webpack resolves the
defaults, which makes the auto detection see a loader for `.css` and `.html`.
The Vue template also needs `experimentalInlineMatchResource` in vue-loader,
required with `experiments.css`.

The "Do you want to extract CSS into separate files?" prompt is gone, native CSS
always emits separate files, and the `htmlWebpackPlugin` answer is now `html`.

* feat(create-webpack-app): stop asking about HTML and CSS

webpack handles both out of the box, so the templates no longer ask whether
to simplify HTML creation, which CSS solution to use, whether PostCSS is
wanted or whether CSS should be extracted. `index.html` is always the entry
point, a stylesheet is always scaffolded, and one question remains for the
preprocessors webpack does not cover, wired through a `type: "css/auto"`
rule that adds only sass-loader/less-loader/stylus-loader.

Also fixes what the generated projects needed to build and run: `baseUrl`
for the Vue TypeScript `paths`, a fully specified `./router/index.js` import
under `"type": "module"`, Svelte 5's `mount()` instead of `new App()`, and
style-module declarations for the TypeScript templates.

* feat(create-webpack-app): keep PostCSS, on its own or over a preprocessor

The single CSS question now lists every tool webpack does not cover itself:
PostCSS, Sass, Less, Stylus, and each preprocessor combined with PostCSS.
A preprocessor rule then reads `use: ["postcss-loader", "sass-loader"]`, which
webpack applies right to left, so the stylesheet is compiled first and PostCSS
runs over the result. PostCSS also scaffolds `postcss.config.js` — in every
template now, not just the default one — and asks for `experiments.css`, since
its `.css` rule turns the automatic detection off.

Covers the answer handling with a test that builds each generator's action
list without running it, so all four templates and all eight answers are
exercised in a second instead of an install apiece.

* feat(create-webpack-app): scaffold TypeScript on webpack's own support

The default template no longer installs ts-loader or registers a rule for it:
webpack strips the types itself. `typescript` stays for the editor and for the
`check:types` script (`tsc --noEmit`, since the build type checks nothing),
`tsconfig.json` gains `noEmit`, and `package.json` records the Node.js floor
type stripping needs. This also gets the template off ts-loader 9, which
crashes on TypeScript 7.

The React, Vue and Svelte templates keep ts-loader: stripping handles neither
`.tsx` nor the single-file components those loaders produce.

* feat(create-webpack-app): ask how TypeScript should be compiled

Type stripping is erasable syntax only and checks nothing, so a project that
wants type checking, decorators, enums or `.tsx` still needs a loader. The
default template asks which to use and defaults to webpack's built-in support;
`ts-loader` restores the rule and the dependency.

Every template that installs ts-loader now pins `typescript@5` with it: its
latest release declares `typescript: "*"` but throws `Cannot read properties
of undefined (reading 'fileExists')` on TypeScript 7. `tsconfig.json` also
loses `noEmit`, which stopped ts-loader from emitting anything; `check:types`
passes the flag itself.

* feat(create-webpack-app): say what each TypeScript compiler choice means

"built-in" and "ts-loader" named the mechanism but not the trade-off, so the
prompt now spells it out: webpack strips types with no type checking and needs
Node.js >= 22.6, while ts-loader type checks as it builds and handles `.tsx`,
enums and decorators. The stored answers are unchanged.

* feat(create-webpack-app): pin typescript@6 with ts-loader, not typescript@5

6.0.3 is the last release of the JavaScript line, and ts-loader 9 builds and
type checks against it; only TypeScript 7, the native port, breaks it. Pinning
the newest version that works keeps the scaffold current.

* fix(create-webpack-app): drop the Vue baseUrl that TypeScript 6 rejects

`baseUrl` is deprecated in TypeScript 6, so every module in the Vue
TypeScript project failed with TS5101 once the pin moved to 6. A `paths`
mapping needs no `baseUrl` when it is relative, which is also what fixed
the TS5090 the option was added for.

* build(deps): update dependencies (except those requiring Node.js > 20)

Refresh every dependency whose new version still runs on the Node.js baseline
the packages declare (>=20.9.0) and CI tests: eslint, webpack, sass, cspell,
prettier, lint-staged, js-yaml, tsx, @swc/core, @types/node, @inquirer/*,
webpack-bundle-analyzer and pkg-pr-new.

webpack 5.110 strips TypeScript types through `module.stripTypeScriptTypes`,
so builds of a `.ts` entry now carry Node's experimental-API warning on
stderr. That is upstream behaviour the CLI should not hide, so the config
format tests filter the warning instead of asserting an empty stderr.

Also accept `toml@5` as a peer dependency — its `parse` export is unchanged,
which is all the on-demand loader uses.

Held back, each needing a Node.js newer than the declared baseline: commander
15 (>=22.12, and a runtime dependency of both published packages), execa 10
(>=22), @changesets/cli 3 and @changesets/get-github-info 1 (^22.11 || ^24 ||
>=26). TypeScript 7 is held back too: typescript-eslint does not support it
yet, so `lint:code` refuses to run.

* build(deps): update changesets to v3

The release workflow runs on `lts/*`, which satisfies the Node.js the new
major asks for (^22.11 || ^24 || >=26).

`@changesets/get-github-info` v1 reshaped its API: `getInfo` is now
`getCommitInfo`, `getInfoFromPullRequest` is `getPullRequestInfo`, both return
`{commit, pull, author}` objects carrying a `markdownLink` instead of a flat
`links` map, and either can return undefined when the commit or pull request
is not found. The changelog generator follows, and keeps its output
byte-identical for every entry shape it handles.

Also point the config `$schema` at `@changesets/config@4.0.0`, which the new
major ships.

* ci: raise the heap for the coverage run

`.c8rc.json` sets `exclude-after-remap`, so c8 source-map remaps every
script V8 reported — all of node_modules included — before applying its
`packages/*/src` include filter. On macOS runners that peaked at 2033 MB
against Node.js 20's 2078 MB default cap: every test passed and the process
then died merging coverage.

Updating webpack to 5.110 grows what has to be remapped (measured over
`test/build/config-format`: 99 MB of V8 coverage across 55 files before,
103 MB across 60 after), which is more than the 45 MB of headroom that job
had left. Node.js 22 and newer, and the Linux and Windows runners, have room
to spare and were unaffected.

v2 renamed every input this workflow passes, so the release job has failed
since the action was bumped in #4831: `version` is `version-script`,
`publish` is `publish-script`, `commit` is `commit-message` and `title` is
`pr-title`.

Note the action's own error message misspells one of them as
`commit-mesage`; `action.yml` at the pinned commit spells it
`commit-message`, and taking the error at its word would silently restore
the default "Version Packages" commit message.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>