-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
[Bug] Nx unable to find fvm despite being present in path #173
Comments
Hi @rohitsrao , Thanks for using the plugin and for reporting this. Can you confirm that |
Hi @tinesoft . Thanks for the fast reply. I am able to do that and get the following output
|
Humm 🤔...this looks like a bug indeed. Can you add the I'll have a look at it |
Thanks. Here you go.
|
Ok thanks! I'll have a look tonight. |
Should nx-flutter be installed globally ? When I ran
So I installed it with I installed it globally in a different attempt but I get the following error
|
Nx-flutter is a dev dependency in your workspace, so it can/must be installed in the root |
Hi @rohitsrao Ok I've just re-read the installation instruction for fvm/flutter https://fvm.app/docs/getting_started/installation/
(emphasis are mine) This means you need to install a main version of flutter. Then use And the the command to use to check the right setup is Can you try that please and let me know? |
@tinesoft Thanks. It is working now. |
Awesome! I'm closing this then |
Plugin Name
@nxrocks/nx-flutter
Nx Report
Expected Behaviour
Expected plugin to create a flutter app using fvm
Actual Behaviour
> NX 'fvm' was not found on your system's PATH.
Please make sure you have installed it correctly.
👉🏾 https://fvm.app/docs/getting_started/installation
Pass --verbose to see the stacktrace.
I have installed fvm using homebrew and fvm is located at
/opt/homebrew/bin/fvm
and myPATH
includes/opt/homebrew/bin:/opt/homebrew/sbin
Steps to reproduce the behaviour
1 - ran
pnpm nx g @nxrocks/nx-flutter:create
2 - selected yes for the option "Are you using Flutter Version Manager"
The text was updated successfully, but these errors were encountered: