Closed ettmetal closed 3 years ago
Thanks @ettmetal, you beat me to it. Ideally it would work with Node 17, but also needs a safer range, will look into this shortly.
Hi @ettmetal, thanks again, this has now been tweaked to the following pattern, Keystone has also been updated - https://github.com/keystonejs/keystone-6-heroku-example/commit/64db1553254bfc9377217fa6d246d47515ca01f8
This should solve #5, allowing deployment via the Heroku button.
A carent range will prevent it working on newer major versions of node than 14, but will allow it to work on any minor / patch version greater than or equal to 14.13, as declared previously.
It seems some part of the process on Heroku is declaring it 'unsafe' to spcify that the app will continue to work on possibly unknown future versions. In testing, this results in the deployment of keystoneJS into Heroku sucessfully.