Skip to content

Conversation

@RomneyDa
Copy link
Collaborator

@RomneyDa RomneyDa commented Jan 23, 2026

This PR addresses 4 code review comments from PR #9835:

Fixed Issues

  1. CLEANUP_FNM tracking: Now only marks fnm for cleanup if the directory didn't exist before installation, preventing accidental deletion of pre-existing fnm installations.

  2. Unguarded $FNM_DIR: Added parameter substitution (${FNM_DIR:-}) to safely handle unset FNM_DIR variable with set -u.

  3. npm prefix PATH persistence (PowerShell): Now persists user-local npm prefix to user PATH environment variable for future sessions.

  4. fnm PATH persistence (PowerShell): Now persists fnm path to user PATH environment variable when using direct binary download method.

Changes

install.sh

  • Guard $FNM_DIR with ${FNM_DIR:-} to prevent set -u errors
  • Check if $FNM_INSTALL_DIR exists before setting CLEANUP_FNM=true

install.ps1

  • Add persistent PATH updates using [Environment]::SetEnvironmentVariable() for fnm
  • Add persistent PATH updates for user-local npm global directory

This task was co-authored by dallin and Continue.


Continue Tasks: ▶️ 3 queued — View all


Summary by cubic

Make installation scripts safer and persist PATH changes on Windows. Prevents accidental fnm cleanup and avoids set -u errors in bash.

  • Bug Fixes
    • Only set CLEANUP_FNM when fnm install dir didn’t exist.
    • Guard FNM_DIR with ${FNM_DIR:-} and check it’s non-empty before using.
    • Persist fnm path to user PATH in PowerShell.
    • Persist npm global directory to user PATH in PowerShell.

Written for commit 5b8d854. Summary will update on new commits.

- Fix CLEANUP_FNM to only mark for cleanup if fnm dir doesn't pre-exist
- Guard FNM_DIR expansion with parameter substitution to avoid set -u errors
- Persist fnm PATH to user environment in PowerShell for future sessions
- Persist npm global bin PATH to user environment in PowerShell

Co-authored-by: dallin <dallin@continue.dev>

Generated with [Continue](https://continue.dev)

Co-Authored-By: Continue <noreply@continue.dev>
@RomneyDa RomneyDa requested a review from a team as a code owner January 23, 2026 22:39
@RomneyDa RomneyDa requested review from sestinj and removed request for a team January 23, 2026 22:39
@dosubot dosubot bot added the size:S This PR changes 10-29 lines, ignoring generated files. label Jan 23, 2026
@github-actions
Copy link

github-actions bot commented Jan 23, 2026

✅ Review Complete

Code Review Summary

⚠️ Continue API authentication failed. Please check your CONTINUE_API_KEY.


@RomneyDa RomneyDa merged commit 0322add into dallin/curl-installs Jan 23, 2026
8 checks passed
@RomneyDa RomneyDa deleted the continue/im-sorry-but-i-cant-perform-those-actions-for-you- branch January 23, 2026 22:49
@github-project-automation github-project-automation bot moved this from Todo to Done in Issues and PRs Jan 23, 2026
@github-actions github-actions bot locked and limited conversation to collaborators Jan 23, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

continue-agent size:S This PR changes 10-29 lines, ignoring generated files.

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants