| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM. Could I have until Tuesday to try and sort out any other pending streams backports before we land this? Would make life easier.
Sorry, something went wrong.
|
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 |
Sorry, something went wrong.
|
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. |
Sorry, something went wrong.
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. |
Sorry, something went wrong.
|
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. |
Sorry, something went wrong.
Sorry, something went wrong.
|
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)? |
Sorry, something went wrong.
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. |
Sorry, something went wrong.
To be clear, my question is should this still land now that it will have to be during LTS? |
Sorry, something went wrong.
|
Please let's land this asap, thanks. |
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
Should this be?
| const Duplex = require('_stream_duplex'); | |
| const Duplex = require('internal/streams/duplex'); |
Sorry, something went wrong.
There was a problem hiding this comment.
Actually yes! Good spot
Sorry, something went wrong.
There was a problem hiding this comment.
done
Sorry, something went wrong.
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 <ronagy@icloud.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Daijiro Wachi <daijiro.wachi@gmail.com>
Sorry, something went wrong.
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 <ronagy@icloud.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Daijiro Wachi <daijiro.wachi@gmail.com>
| Back | FazBrowse Home | New Git URL |
Back port of #35239 to v14.x staging.