-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting Dev Issues
Kevin Berry edited this page Sep 24, 2022
·
4 revisions
NOTE: This information may no longer be valid... Atoll has moved over to Node 16+ and this was probably contributed at a time when either Node v10 or v12 was used by Atoll.
If the database isn't being created it could be the version of Node that's the problem. See the npm start
output below for the typical output. If you don't see the database scripts executing then it could be the
version of Node that's the problem: v14.x causes silent failures and the script output isn't shown like this.