Summary:
Added a check if node -v can be executed with-out a failure. If it fails it will show an error dialog and direct the user to README.md installation section.
It also adds a new property to Mixpanel so we know the used Node.js version & if node is missing. So we know how often it happens that a user starts Guppy with-out installing Node.js first.
(Maybe we have to update our privacy.md to have the new information there.)
The local state isNodeMissing is used to disable the Create new project wizard. The create button won't have an effect - we could add a tooltip there & disable the button but I'm not sure if it's worth it to add. As this is a very rare use-case, node not installed and then clicking around in the app.
How to test?
I've tested it on Windows by renaming the path to Node binary. e.g. C:\Program Files\nodejs\missing.
Then start the Guppy binary to see the dialog from the screenshot below & the redirection.
Related Issue:
263
Summary: Added a check if
node -vcan be executed with-out a failure. If it fails it will show an error dialog and direct the user toREADME.mdinstallation section.It also adds a new property to
Mixpanelso we know the used Node.js version & if node is missing. So we know how often it happens that a user starts Guppy with-out installing Node.js first. (Maybe we have to update our privacy.md to have the new information there.)The local state
isNodeMissingis used to disable theCreate new project wizard. The create button won't have an effect - we could add a tooltip there & disable the button but I'm not sure if it's worth it to add. As this is a very rare use-case, node not installed and then clicking around in the app.How to test? I've tested it on Windows by renaming the path to Node binary. e.g.
C:\Program Files\nodejs\missing. Then start the Guppy binary to see the dialog from the screenshot below & the redirection.Screenshots/GIFs:
Mixpanel Product dashboard: