We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
latest
linux
unjs/h3#940
With unjs/h3 server
Work without call of stream.write() if run with bun dev not work if run with bun -b dev. To work need to add stream.write().
stream.write()
bun dev
bun -b dev
const sse = require('https://github.com/EventSource/node-ssestream/blob/master/index.ts'); const rxjs_1 = require("rxjs"); const operators_1 = require("rxjs/operators"); const stream = new sse.SseStream(request); stream.pipe(response, options); // stream.write(''); const subscription = result .pipe((0, operators_1.map)((message) => { if ((0, shared_utils_1.isObject)(message)) { return message; } return { data: message }; }), (0, operators_1.concatMap)(message => new Promise(resolve => stream.writeMessage( message, () => resolve()))), (0, operators_1.catchError )(err => { const data = err instanceof Error ? err.message : err; stream.writeMessage({ type: 'error', data }, writeError => { if (writeError) { this.logger.error(writeError); } }); return rxjs_1.EMPTY; })) .subscribe({ complete: () => { response.end(); }, }); request.on('close', () => { subscription.unsubscribe(); if (!stream.writableEnded) { stream.end(); } });
200 ok
204 no content
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What version of Bun is running?
latest
What platform is your computer?
linux
What steps can reproduce the bug?
unjs/h3#940
With unjs/h3 server
Work without call of
stream.write()
if run withbun dev
not work if run withbun -b dev
. To work need to addstream.write()
.What is the expected behavior?
200 ok
What do you see instead?
204 no content
Additional information
No response
The text was updated successfully, but these errors were encountered: