Before this change we do a greedy check against ALL package.json files. We had thought that every package.json would need to follow the same dependency rules, but now with the introduction of client extensions, these package.json files will work within their own "workspace" and is isolated from liferay-portal. So now we check if the package.json has a sibling yarn.lock file, and if it does then we don't worry about that project.
Before this change we do a greedy check against ALL package.json files. We had thought that every package.json would need to follow the same dependency rules, but now with the introduction of client extensions, these package.json files will work within their own "workspace" and is isolated from liferay-portal. So now we check if the package.json has a sibling yarn.lock file, and if it does then we don't worry about that project.