Repository navigation
Conversation
Node.js versions below 10.x are not maintained anymore, so it is probably best to use some newer, still maintained versions. For release cyles of Node.js see the official site: <https://nodejs.org/en/about/releases/>.
Node.js versions below 10.x are not maintained anymore, so it is probably best to use some newer, still maintained versions.
AppVeyor cannot find a matching package to install for Node 16, so do not use it on AppVeyor. For an example of that problem see <https://ci.appveyor.com/project/browserify/browserify/builds/39074493/job/f56gjo1d8f1odghj>
Change requested by @ljharb, so let's do this.
|
Since there has been no activity here for almost a week: Is there anything else blocking this PR? Any more change requests? If so, please let me know. |
Good. Since this pull request has been approved one and a half month ago but it has not been merged yet: Is there anything else to do? If not, can someone merge it please? |
|
@striezel tests are failing on master in node < 4, and altho i reviewed this PR, i don't typically maintain browserify, so it needs to wait for the maintainers. |
|
@goto-bus-stop or who is currently maintaining browserify: Is there a chance to get a review on the changes? Is this still relevant after almost a year now? |
This comment was marked as spam.
This comment was marked as spam.
|
@ljharb @goto-bus-stop @feross Would dropping 0.10 and 0.12 be up for reconsideration alongside #2070 ? Split that out to #2071, which does not overlap with this PR. |
|
Nope, we will continue to support them. |
4 participants
Node.js versions below 10.x are not maintained anymore, so it is probably best to use some newer, still maintained versions.
For release cyles of Node.js see the official site: https://nodejs.org/en/about/releases/.