Experimental Microsoft.AspNetCore.ClientAssets and multi-target framework builds fails

[dp-sgr]

At first:

I really love the Microsoft.AspNetCore.ClientAssets package. Its wonderful to automate everything that has to do with static web assets.
As stateted in #38445 we may get a implementation direkty into the SDK. This would also be wonderful.

The current Issue:
As we started using .NET7 we needed to implement some Workarounds. So our RCL now targets net6 & net7.
Since then we get Build Errors from time to time (Sporadically).
It seems that the Mutli-Target build runs npm install two times. If this would not be parallel everything would be ok for me. But it seems that the install will be invoked in parallel (or at least slighty one after another) without waiting the first invocation to be completed. And this leads to the current error.

For now i adjusted my build process and disabled parallel building with BuildInParallel set to false:
https://learn.microsoft.com/en-us/visualstudio/msbuild/building-multiple-projects-in-parallel-with-msbuild?view=vs-2022

So i got an Workaround up-and running fine for me.
This Issue is just an Info for you to also pay attention to in the new integration.

Thanks for your good work :)
I'm hyped to get my hands on the SDK integrated Version

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.