version-fox / version-fox/vfox-flutter
[BUG]: After using vfox activate, the global option becomes invalid.
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 2
- Forks
- 7
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 6
Description
Version
1.0.11
OS
Win11
Describe the bug
After adding Invoke-Expression "$(vfox activate pwsh)" to my POWERSHELL $PROFILE, I ran vfox use -g flutter@3.41.9. When I then called flutter, I got the error:
flutter: The term 'flutter' is not recognized as a name of a cmdlet, function, script file, or executable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
If I remove the Invoke-Expression "$(vfox activate pwsh)" line, flutter works normally, but then vfox use -p has no effect.
Screenshots[optional]
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue on Windows 11 using the PowerShell $PROFILE entry and the vfox activate pwsh, vfox use -g flutter@3.41.9, and vfox use -p commands. Trace the activation entry point and verify that both global Flutter selection and project selection leave flutter available in PowerShell; done when the reported command works in both setups.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flutter, lua, powershell
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100