Challenges when running multi-project apps simultaneously resulting in 504 Outdated Optimize Dep errors #28536
Labels
angular/build:dev-server
area: @angular/build
needs: investigation
Requires some digging to determine if action is needed
Comments
alan-agius4
added
needs: investigation
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Oct 1, 2024
Previously, Vite prebundled dependencies were stored in a shared directory across all projects, which caused the `_metadata.json` files to be overwritten. This resulted in undefined behavior, such as re-optimizing dependencies on each run when multiple projects were present in the workspace. Additionally, it introduced conflicts when running multiple `ng serve` processes simultaneously. Closes angular#28536
alan-agius4
added a commit
that referenced
this issue
Oct 1, 2024
Previously, Vite prebundled dependencies were stored in a shared directory across all projects, which caused the `_metadata.json` files to be overwritten. This resulted in undefined behavior, such as re-optimizing dependencies on each run when multiple projects were present in the workspace. Additionally, it introduced conflicts when running multiple `ng serve` processes simultaneously. Closes #28536 (cherry picked from commit c0b76e3)
|
Thank you for the prompt fix @alan-agius4 we spent several days trying to resolve this thinking we'd got something configured incorrectly 🤣🤣 |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Command
serve
Is this a regression?
The previous version in which this bug was not present was
No response
Description
We have a multi-project Angular workspace which contains 3 servable apps and several shared libraries. One app is the Identity App and we need to run this and one of the other apps which provide features. I start up the Identity App first and then run the Feature App.
Each time I run ng serve for the Identity App I get a folder in .angular\cache\18.2.5\vite which is named deps_temp_#hash where the hash is different each time. If I run this with a completely empty cache folder every time I run ng serve I get another folder created.
I then run ng serve for the Feature App and I get a similar folder but it quickly disappears and I get a deps folder but all of the temp folders for the Identity App remain.
Typically on first run I now get an error in the Network tab of Chrome DevTools with 504 error always on a file called
browser-#hash.js?v=#hash. Upon rerunning ng serve the problem can go away and sometimes it's very difficult to replicate again and then other times it happens all the time. The browser file is requested from disk from the vite cache and it never exists within the cache itself.Obviously the app is rendered useless when it does happen.
I understand without a repo that replicates this its going to be very difficult to diagnose however I was hoping that somebody with a little more knowledge than myself of this tooling process could provide some guidance as we have come to a full-stop on it other than disabling the cache or just living with the problem.
Minimal Reproduction
Unfortunately I haven't as yet managed to replicate the problem in an example setup outside of our live application. The application uses Duende Identity server and ASP.NET Core minimal API projects along with multiple SQL databases etc. so its not an easy thing to replicate in its entirety.
Exception or Error
Your Environment
tsconfig.json
The text was updated successfully, but these errors were encountered: