vite-plugins

Closes #369. Summary replace the native constructor identity check with a structural check for the response interface consumed by the Node.js adapter keep forwarding invalid application return values to Vite's error handler add an end-to-end regression test using from add a patch changeset This allows Fetch API-compatible implementations such as the response returned by GraphQL Yoga to work without requiring applications to recreate them with Node.js's global constructor. The existing check was introduced in #45 to reject invalid return values such as strings, and #63 later routed those values through Vite's error handler. This change preserves that behavior while replacing constructor identity with an interface check, so compatible Response implementations are not treated as application errors. Tests

Description rejects Fetch API-compatible objects when they were created by a different implementation than Node.js's global constructor. The dev server currently checks the response with: This makes constructor identity part of the contract. A response from , for example, exposes the standard response fields and methods but is not an instance of Node.js's built-in class. The plugin therefore forwards a successful HTTP response to Vite's error handler, which renders an error such as: This occurs in practice with GraphQL Yoga, which can return through / . Minimal reproduction Start Vite and request . The application returns a valid response, but the dev server reports it as an unknown error. Expected behavior The dev server should accept Fetch API-compatible responses from other implementations. If requires a native Node.js , the plugin can normalize a compatible response into one while preserving its body, status, status text, and headers. Invalid return values should continue to reach Vite's error handler as they do today. Environment : 0.26.1 : 0.9.0 Node.js: reproducible on supported Node.js versions with built-in Fetch API support