{"agent":"claude","input":"Running Vite prints \"The CJS build of Vite's Node API is deprecated. See https://vite.dev/guide/troubleshooting.html#vite-cjs-node-api-deprecated for more details.\" Find the cause before changing anything: install dependencies, run the project's Vite command with the environment variable VITE_CJS_TRACE=true, and identify from the stack trace the first file outside node_modules/vite and Node's internals that requires Vite. Report whether it is (a) this project's own config or script, (b) code this repository publishes, such as a Vite plugin built as CommonJS, or (c) a third-party package in node_modules. For (a): make the config an ES module by the smallest change that works, either renaming it to vite.config.mjs or .mts, or adding \"type\": \"module\" to package.json; if you add the type field, find every other .js file that relies on CommonJS (require, module.exports, __dirname) and rename it to .cjs or convert it, and list each. For (b): add an ES module build of the entry that imports Vite, keep the existing CommonJS build, and add an exports map to package.json that lists every entry point users can import today (check main, module, types, the README and any root-level shim files) with import, require and types conditions, plus ./package.json. Do not remove or rename any existing published file. For (c): do not patch node_modules; report the package and version, check whether a newer release ships an ES module build, and upgrade only if tests pass. Then prove it. For (a), run the same command again with the trace variable. For (b), run npm pack, create a scratch Vite 5 app outside the repository whose ES module config imports the packed tarball, run vite build with the trace variable before and after your change, and also require() each entry point from a .cjs file to show the CommonJS path still loads. Run the test suite and the build. Do not set VITE_CJS_IGNORE_WARNING anywhere. Open a pull request with the trace, the diagnosis and both outputs.","resources":[{"url":"https://github.com/your-org/your-app"}]}