A list of common issues that developers face and how to resolve them.
This could happen if node modules were compiled with a different version of node, or if node modules fail to compile due to other configuration errors.
Running tests locally requires node
to specifically be the latest version of NodeJS 14. You can use nvm
to manually set the node version.
Run the following commands to set the node version and then re-install the node modules:
nvm use 14
rm -r node_modules
npm install
On your Docker application, go to Preferences > Resources and increase the amount of memory allocated for Docker.
If you cannot login to the app and see an MongoError: not primary and secondaryOk=false
error in the console, then your Mongo container is configured incorrectly.
This is most likely due to the replicaSet being misconfigured with the wrong IP address of the MongoDB container.
This should only happen if your MongoDB volume was created before #4603.
To fix this issue, either delete and re-create the MongoDB volume, or follow these steps:
- Login to the docker container using
docker exec -it <mongodb-container-id> /bin/sh
- Start the mongodb shell with
mongosh
. - Run the following commands within
mongosh
to force set the IP address within the replica set:
conf = rs.config()
conf.members[0].host = 'database:27017'
rs.reconfig(conf, {force:true})
Make sure nvm
is loaded to the environment in ~/.bash_profile
. To do so, the ~/.bash_profile
should include the following lines:
export NVM_DIR=~/.nvm
source $(brew --prefix nvm)/nvm.sh
Ensure that on startup, brew
is added to the environment variables and ~/.bash_profile
is run. To do so, ~/.zshrc
should have the following lines:
export PATH=/opt/homebrew/bin:$PATH
source ~/.bash_profile