Skip to content
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

Don't perform any changes when trying to use current node version #1161

Merged
merged 1 commit into from
Sep 10, 2024

Conversation

CyBot
Copy link
Contributor

@CyBot CyBot commented Aug 2, 2024

Implements the change suggested by @danielkcz in #16 (#16 (comment))

Makes it more convenient to automatically switch current node version #

Copy link

github-actions bot commented Sep 2, 2024

This PR is stale because it has been open 45 days with no activity.

@github-actions github-actions bot added the Stale Stale label Sep 2, 2024
Copy link

@mperzz mperzz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

// Check if a change is needed
curVersion, curCpuarch := node.GetCurrentVersion()
if version == curVersion && cpuarch == curCpuarch {
fmt.Println("node v" + version + " (" + cpuarch + "-bit) is already in use.")
return
}

// Make sure the version is installed. If not, warn.
if !node.IsVersionInstalled(env.root, version, cpuarch) {
	fmt.Println("node v" + version + " (" + cpuarch + "-bit) is not installed.")

PERFECT

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Stale Stale
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants