Specify the requirements #28

Activity

1. gido

   assigned

   Yago

   on Mar 21, 2018
2. Yago commented on Mar 23, 2018

   

   Yago

   on Mar 23, 2018

   Member

   More actions

   Indeed, I saw that the last major version of our generator doesn't have the engine specified in the package.json.

   I don't completely agree with the fact that we have to support a big range of Node's versions. Actually, the LTS (stable for prod) is in 8.10.0 and as you said, under 8.0.0, there is no async support, it's a bit the Middle Ages of JavaScript and we must live in the present 😉

   We have to readd the engine definition in the package.json project with something like :

   "engines": {
     "node": ">=8.0.0",
     "npm": ">=5.0.0"
   },
3. gido commented on Mar 25, 2018

   

   gido

   on Mar 25, 2018

   Last edited by gido

   Author

   More actions

   +1 for defining the requirement in the package.json

   6.x is still Active until the end of April 2018 and will be maintained until April 2019. So it's not really the Middle Ages of Javascript ;-)

   
   (source)

   I agree we must live in the present but think also of the past and don't drop to easily active/maintained version of nodejs without a good reason.
4. tonifisler commented on May 21, 2019

   

   tonifisler

   on May 21, 2019

   Member

   More actions

   This needs to be fixed, it's quite annoying. As @knuch said in #36, if you don't work with Node 12, it's broken. SMH
5. Yago commented on May 21, 2019

   

   Yago

   on May 21, 2019

   Last edited by Yago

   Member

   More actions

   The weird fact is that I still haven't Node 12 installed on my Mac (even on the last contrib) 😅
6. Yago commented on May 21, 2019

   

   Yago

   on May 21, 2019

   Member

   More actions

   “it's broken” is not very relevant... What's broken exactly ?