npm v7 workspace dependencies not bundled about serverless-layers

[georgethomasuk]

I think I have run into the same thing just with Yarn, as I have been relying on having local packages within the workspace without them being referenced in the package.json.

I tried looking for a command in the package manager that I could use as a customInstallationCommand to resolve the dependencies, as it feels like something you would ideally delegate to the package manager. However, I could not find anything.

I did, however, develop a hacky workaround to unblock myself in the short term. Basically creating a temporary package.json that merges the main project and the local packages dependencies together as part of the deployment process, then restore the original at the end. This approach is full of holes but might help unblock someone in the short run. The same principles should work for yarn and npm:

...
"scripts": {
    "generate-merged": "package-json-merge ./package.json ../../packages/auth/package.json > merged-package.json",
    "backup": "cp package.json backup-package.json",
    "swap": "mv merged-package.json package.json",
    "restore": "cp backup-package.json package.json",
    "predeploy": "yarn generate-merged && yarn backup && yarn swap",
    "deploy": "serverless deploy",
    "postdeploy": "yarn restore"
  }
...

This works as a quick and dirty fix, but I feel like it would be hard to maintain as the dependencies get more complicated. For example, if the local package then depended on another local package.

When I have some time in the next few days I'll try and look into this further to see any solutions inside the package managers.