remote-cache

Which package / area of the repo does the bug impact? @vercel/remote-nx What version are you using? 2.0.0 What package manager are you using / does the bug impact? npm What operating system are you using? Linux Describe the Bug The current release (2.0.0) depends on nx-remotecache-custom v17, which in turn depends on nx 17. When you upgrade to 19 (or 18) you get 2 copies of nx in your dependency tree. There is a new version of for v19. I was able to upgrade my local nx to 19.1, but after that (current version as of this issue is 19.7.x) it seems to be broken - you get strange errors about nx not creating a dependency graph. I suspect the cause is the colliding nx versions.. but even if that wasn't the case, it would be nice to have explicit support so we don't have duplicate copies of nx in our trees. Can we get an update version to support nx 19? Expected Behavior That I can run this with nx 19 To Reproduce create a project with the latest version of nx (19.7.x) and try to run a mult-package command.

Which package / area of the repo does the bug impact? _No response_ What version are you using? @vercel/remote-nx@2.0.0 What package manager are you using / does the bug impact? npm, pnpm, Yarn v1, Yarn v2/v3 What operating system are you using? Mac Describe the Bug As stated above. Building a project on develop and then committing that branch to main makes vercel reuse the existing build, with existing ENV variables from the other environment. This might be the intended behaviour but a heads-up warning on your documentation would be nice indeed. Expected Behavior Inform users about this behaviour To Reproduce Build