Closed shaftoe closed 2 years ago
I'm also getting this message, but just as a warning. Could be because of Node.js v17.2. Can you try it with Node.js v16 (LTS)?
Indeed it seems to be related with Node v17:
diff --git a/package.json b/package.json
index a4ff364..83b358d 100644
--- a/package.json
+++ b/package.json
@@ -103,6 +103,6 @@
]
},
"engines": {
- "node": ">= 14"
+ "node": "16.x"
2021-12-07T15:19:45.538078+00:00 heroku[web.1]: State changed from crashed to starting
2021-12-07T15:19:51.341761+00:00 app[web.1]:
2021-12-07T15:19:51.341773+00:00 app[web.1]: > ackee@3.3.0 server
2021-12-07T15:19:51.341773+00:00 app[web.1]: > node src/index.js
2021-12-07T15:19:51.341773+00:00 app[web.1]:
2021-12-07T15:19:50.079125+00:00 heroku[web.1]: Starting process with command `npm run server`
2021-12-07T15:19:53.065920+00:00 app[web.1]: [Ackee] āŗ ā¦ awaiting Connecting to http://mongodb+srv/admin:XXX/ackee?retryWrites=true&w=majority
2021-12-07T15:19:53.074307+00:00 app[web.1]: (node:22) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./public/" in the "exports" field module resolution of the package at /app/node_modules/extract-files/package.json.
2021-12-07T15:19:53.074309+00:00 app[web.1]: Update this package.json to use a subpath pattern like "./public/*".
2021-12-07T15:19:53.074310+00:00 app[web.1]: (Use `node --trace-deprecation ...` to show where the warning was created)
2021-12-07T15:19:53.874798+00:00 heroku[web.1]: State changed from starting to up
I've updated graphql-tools which was using an old version of extract-files. The next release of Ackee should work with Node.js 17. Thanks for letting me know!
Thank you for the quick feedback
š Describe the bug
Pushing v3.3.0 to Heruku ends in a crash
š To Reproduce
git push -f heroku 615693828bf00a35e57318e109610bfb36138f87:master
š¼ļø Screenshots
āļø Environment
š Additional context
It's been a long time since the last update so I might have forgotten something important in how to upgrade, sorry about that