examples/custom-javascript-parser/webpack.config.js:18

• webpack.config.js now exports a configuration array with no entry for any compiler. Webpack requires an entry point, so running this example via webpack --config webpack.config.js will fail unless callers always provide --entry on the CLI. Consider restoring entry: './example.js' (or setting a shared entry variable) and, if the README build pipeline needs CLI-provided entry/output, update build.js to set global.NO_TARGET_ARGS = true for this example to avoid overriding the per-compiler output.filename settings.

/** @type {import("webpack").Configuration[]} */
const config = [
	// oxc
	{
		mode: "production",
		optimization: {
			chunkIds: "deterministic" // To keep filename consistent between different modes (for example building only)
		},
		output: {
			filename: "oxc.[name].js"
		},
		module: {

examples/custom-javascript-parser/README.md:401

• The README’s embedded Configuration example now shows configs without an entry, which makes the example config incomplete unless users pass --entry on the CLI. Additionally, the Info section shows assets named output.js, which conflicts with the output.filename values shown in the config snippet, making the documentation internally inconsistent. Once the config/build setup is corrected, please regenerate this README section so the shown output matches the configuration.

/** @type {import("webpack").Configuration[]} */
const config = [
	// oxc
	{
		mode: "production",
		optimization: {
			chunkIds: "deterministic" // To keep filename consistent between different modes (for example building only)
		},
		output: {
			filename: "oxc.[name].js"
		},
		module: {