You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 17, 2021. It is now read-only.
Describe the bug
Project creation fails with-out an error message because of an old node version (see screenshot below).
I have to update my VM ware node version.
To Reproduce
Check your node version and use a version <8.10.0 (e.g. 8.9.3) (use nvm)
Enable LOGGING in src/config/app.js
Create a new CRA project
Check the console output
Expected behavior
On app load check that the Node version is matching the required version. If not, display a message and don't render guppy.
Or we could add a check to Project creation for CRA to catch the error, display a message & abort installation.
Version to check see screenshot. Check with semver & check three versions 6 || 8 || 10.
TODOs
Check requirements of Gatsby & Next.js. We have to meet these version too.
Screenshots
Environment (please complete the following information):
OS: Ubutnu 16.04.3 (but will also occur cross-platform)
Version: master
Node version: 8.9.3
The text was updated successfully, but these errors were encountered:
Happy to look into this. Thinking it might be a good place to use the info bar created in #352 to display the error. What do you think?
On app load check that the Node version is matching the required version. If not, display a message and don't render guppy.
I can't seem to see a clear node version that's required to run Guppy, if it can be run on any version then showing the app isn't wrong? What do you think?
Describe the bug
Project creation fails with-out an error message because of an old node version (see screenshot below).
I have to update my VM ware node version.
To Reproduce
src/config/app.js
Expected behavior
6 || 8 || 10
.TODOs
Screenshots
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: