fix: .ts extension error in vite.config.ts

[sarthakNITT]

• prior script was showing .ts extension error on running bun run dev with node version v20.19.0
• before:

• after:

Closes #1561

[Copilot]

Pull request overview

This PR updates the Whispering app’s dev script to run Vite through Bun, addressing a Node v20 ERR_UNKNOWN_FILE_EXTENSION error when vite.config.ts is loaded during local development (Closes #1561).

Changes:

• Update apps/whispering’s dev:web script from vite dev to bun --bun vite dev to avoid the .ts config extension error.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[thisisharsh7]

hey @sarthakNITT thanks for the fix. could you also apply the same changes to these apps?

epicenter/apps/fuji/package.json

Lines 7 to 9 in 6094317

	"dev": "vite dev",
	"build": "NODE_ENV=production vite build",
	"preview": "vite preview",

epicenter/apps/honeycrisp/package.json

Lines 10 to 12 in 6094317

	"dev": "vite dev",
	"build": "NODE_ENV=production vite build",
	"preview": "vite preview",

[sarthakNITT]

@thisisharsh7 Done.

[thisisharsh7]

thanks a lot! braden will do the final review 👍

[sarthakNITT]

Sure.

[sarthakNITT]

@thisisharsh7 Sorry, I missed that. I've fixed code as per review👍

[Leftium]

Hey @sarthakNITT, thanks for the PR! The root cause here is actually a missing dependency: apps/fuji/vite.config.ts imports from @epicenter/constants/apps, but @epicenter/constants isn't listed in fuji's package.json. Same likely applies to the other apps.

Adding "@epicenter/constants": "workspace:*" to devDependencies and running bun install fixes it without needing bun --bun. The bun --bun flag works around the issue because Bun's resolver is more lenient with workspace packages, but Node's resolver (which Vite uses by default) requires the dependency to be explicitly declared and linked.