You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The steps outlined in the "Local development with Docker" section of the README do not result in a functional local development environment. After performing docker compose up in Step 1, I receive two errors related to node_modules missing in the API/Web container(s).
To Reproduce
Clone the NRM-Grants-Agreement to your computer and change directory into the newly cloned project folder.
Follow Step 1 of the "Local development With Docker" section of the README and execute the command docker compose up.
Observe that you receive errors on the screen (and in the log) from api_1 and web_1 shells stating that nodemon and ng commands were not found. The errors point to the fact that a package.json exists but that the node_modules directory is not present.
Expected behavior
A successful execution of step 1 is expected without the listed errors being present in the terminal/log. The user is ready to continue on to the second step of the README.
Actual behavior
Errors are encountered as part of step 1 related to node_modules missing. These errors can be seen in this terminal output log.
Desktop (please complete the following information):
OS: MacOS Big Sur 11.5.2
Additional context
An npm install somewhere in the container setup process might take care of this bug, that will at least resolve the missing node_modules folder.
Describe the bug
The steps outlined in the "Local development with Docker" section of the README do not result in a functional local development environment. After performing
docker compose upin Step 1, I receive two errors related tonode_modulesmissing in the API/Web container(s).To Reproduce
docker compose up.api_1andweb_1shells stating thatnodemonandngcommands were not found. The errors point to the fact that apackage.jsonexists but that thenode_modulesdirectory is not present.Expected behavior
A successful execution of step 1 is expected without the listed errors being present in the terminal/log. The user is ready to continue on to the second step of the README.
Actual behavior
Errors are encountered as part of step 1 related to
node_modulesmissing. These errors can be seen in this terminal output log.Desktop (please complete the following information):
Additional context
An
npm installsomewhere in the container setup process might take care of this bug, that will at least resolve the missingnode_modulesfolder.