-
Notifications
You must be signed in to change notification settings - Fork 29.6k
New issue
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
[v14.x] stream: move to internal/streams #35349
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Could I have until Tuesday to try and sort out any other pending streams backports before we land this? Would make life easier.
I'm in the process of preparing the 14.x release. Sounds like there are some other commits that need to land first? If this is ready to land and definitely should go out today please let me know ASAP |
I would prefer this to ship before v14 goes LTS as it would help with readable-stream. Overall, it can wait a week or two. @ronag which PRs? Note that I had to redo the work for the backport because of the conflicts, so you might want to do a single backport PR with a few commits in. |
Ah let's do it like that. I can open backports later when I get the chance. A little short on time at the moment. |
This was not backported yet by any other PR.. I think it's really important to have this in the latest v14.x release before LTS. cc @ronag @BethGriggs @ronag. |
4f7b517
to
0b0ea8b
Compare
also cc @MylesBorins |
The v14.15.0 LTS transition release (#35746) is due to go out today. Although it would have been ideal to land this PR before LTS, do you think it can still land post-LTS (in the next release)? |
Just to be clear, the last Node.js 14.x before LTS was 14.14.0 on 15 Oct. The LTS transition release is going to happen today, releases have already been successfully built and awaiting promotion (which I'll do during this afternoon's Release WG mentoring session). So this can only land in 14.x post-LTS. |
To be clear, my question is should this still land now that it will have to be during LTS? |
Please let's land this asap, thanks. |
This comment has been minimized.
This comment has been minimized.
lib/internal/streams/transform.js
Outdated
ERR_TRANSFORM_ALREADY_TRANSFORMING, | ||
ERR_TRANSFORM_WITH_LENGTH_0 | ||
} = require('internal/errors').codes; | ||
const Duplex = require('_stream_duplex'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be?
const Duplex = require('_stream_duplex'); | |
const Duplex = require('internal/streams/duplex'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually yes! Good spot
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
Move all the streams constructors to internal/streams and avoid a circular dependencies between the modules. See: nodejs/readable-stream#348 PR-URL: nodejs#35239 Reviewed-By: Robert Nagy <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Daijiro Wachi <[email protected]>
0b0ea8b
to
6f99bd1
Compare
Move all the streams constructors to internal/streams and avoid a circular dependencies between the modules. See: nodejs/readable-stream#348 PR-URL: #35239 Backport-PR-URL: #35349 Reviewed-By: Robert Nagy <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Daijiro Wachi <[email protected]>
Landed in fb14acb |
Back port of #35239 to v14.x staging.