Skip to content

chore: clean-up code used for Node.js 4 and 5 #4335

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

Merged
merged 1 commit into from
Feb 5, 2019

Conversation

rosen-vladimirov
Copy link
Contributor

In several cases CLI spawns new Node.js processes. On each of these places we have a logic to check if the currently used Node.js version is 4 or 5 and add additional arguments to the process. As we no longer support these versions, clean-up the obsolete logic.

PR Checklist

In several cases CLI spawns new Node.js processes. On each of these places we have a logic to check if the currently used Node.js version is 4 or 5 and add additional arguments to the process. As we no longer support these versions, clean-up the obsolete logic.
@rosen-vladimirov rosen-vladimirov added technical debt no-changelog The issue is present only in `next` versions and was not included in official version. labels Feb 4, 2019
@rosen-vladimirov rosen-vladimirov added this to the 5.2.0 milestone Feb 4, 2019
@rosen-vladimirov rosen-vladimirov self-assigned this Feb 4, 2019
@rosen-vladimirov rosen-vladimirov merged commit 7f479d9 into master Feb 5, 2019
@rosen-vladimirov rosen-vladimirov deleted the vladimirov/clean-up-node-args branch February 5, 2019 08:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-changelog The issue is present only in `next` versions and was not included in official version. technical debt
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants