yarn add not installing the respective node modules after the initial yarn install has been run.

[safang99]

After generating a new project and navigating to the client subfolder to add a specific package with a yarn add command, It will update the /client/package.json and yarn.lock files, but it will not be added to node modules. Running the yarn add command multiple times will appear to keep installing the package and not error out, but again it is never actually added to the node_modules folder. The current solution has been to delete node_modules and yarn.lock and then reinstall. May be an issue with the node_modules/.yarn-integrity check.

yarnpkg/yarn#2240

[dpickett]

I can verify this is occurring in the latest version of engage. I had this challenge when adding objection-unique to a server. so strange.