config handling makes bun and nodemon crazy

[slavaGanzin]

Describe the bug

Hello, thanks for Vite!

vite/packages/vite/src/node/config.ts

Lines 1236 to 1248 in fcf50c2

	if (isESM) {
	const fileBase = `${fileName}.timestamp-${Date.now()}-${Math.random()
	.toString(16)
	.slice(2)}`
	const fileNameTmp = `${fileBase}.mjs`
	const fileUrl = `${pathToFileURL(fileBase)}.mjs`
	await fsp.writeFile(fileNameTmp, bundledCode)
	try {
	return (await import(fileUrl)).default
	} finally {
	fs.unlink(fileNameTmp, () => {}) // Ignore errors
	}
	}

I don't know context, but it's a crazy hack that makes any --watch command go crazy. And you couldn't detect it, because it cover himself with deleting files. "Fortunately", I found out a lot of undeleted Vite.timestamp.mjs files, and I started digging.

Can this files at least be created outside repo?

Reproduction

none

Steps to reproduce

No response

System Info

doesn't matter

Used Package Manager

bun

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[slavaGanzin]

Btw, my package already has {type: 'module'}, so creating .mjs files doesn't make any sense

[bluwy]

This is being tracked at #9470