fix: prevent duplicate manifest generation

[wattanx]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

I want to avoid duplicate generation of client.manifest.
In the case of a webpack production build, the manifest is generated in the following two places:

bridge/packages/bridge/src/module.ts

Lines 128 to 130 in cffcd07

	if (opts.nitro && !nuxt.options.dev && !nuxt.options._prepare) {
	await generateWebpackBuildManifest()
	}

bridge/packages/bridge/src/nitro.ts

Lines 241 to 251 in cffcd07

	nuxt.hook('build:compiled', async ({ name }) => {
	if (nuxt.options._prepare) { return }
	if (name === 'server') {
	const jsServerEntry = resolve(nuxt.options.buildDir, 'dist/server/server.js')
	await fsp.writeFile(jsServerEntry.replace(/.js$/, '.cjs'), 'module.exports = require("./server.js")', 'utf8')
	await fsp.writeFile(jsServerEntry.replace(/.js$/, '.mjs'), 'export { default } from "./server.cjs"', 'utf8')
	} else if (name === 'client') {
	const manifest = await fsp.readFile(resolve(nuxt.options.buildDir, 'dist/server/client.manifest.json'), 'utf8')
	await fsp.writeFile(resolve(nuxt.options.buildDir, 'dist/server/client.manifest.mjs'), 'export default ' + JSON.stringify(normalizeWebpackManifest(JSON.parse(manifest)), null, 2), 'utf8')
	}
	})

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[wattanx]

This PR seems likely to solve the strange issue as well.
In a very large project, we know that this can cause the manifest to break as follows due to its impact.
(It's difficult to create a reproduction because this only occurs in large projects...)

[nitro 18:53:28]  ERROR  RollupError: Unterminated string constant (Note that you need plugins to import files that are not JavaScript)


138909:     "file": "",
138910:     "prefetch": true,
138911:     mports": [
                  ^
138912:       "_4b157d7.js",
138913:       "_c3032ed.js",

Using patch-package, I confirmed that no errors occurred.

[wattanx]

@danielroe
Due to the issues mentioned above, I am considering including it in 3.1.0. Could you please check if there are any problems?

[danielroe]

I don't believe this change is needed.

[wattanx]

Thank you ❤️