William Godbe

Weird, this works for me locally - @javiercn any idea why it might not in CI?

Oh, I see, it's failing on all legs where we don't build NodeJS. So we'd have to turn the Node build on everywhere if we want to not check these...

@javiercn I forgot the email thread about this mentioned needing to check in a lockfile with the closure of dependencies all linux distros might need - can you help with...

> error [email protected]: The engine "node" is incompatible with this module. Expected version ">=12.0.0". Got "10.24.1" This is only happening on Arm - we installed Node 16.x before this. @javiercn...

@javiercn `node --version` on Musl gives the following immediately after installing node 16.x: > /__w/_temp/f5c5264c-3db8-4ff5-8493-cab567b71d45.sh: line 1: /__t/node/16.19.0/x64/bin/node: No such file or directory Even though the preceding installation step claims...

Closing as this is blocked on moving to NPM

Blocked on getting an SDK from https://github.com/dotnet/installer/pull/15151

Here's a new one, will look tomorrow: > /Users/runner/work/1/s/.dotnet/sdk/8.0.100-alpha.1.23054.7/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(90,5): error NETSDK1195: Unable to optimize assemblies for size: a valid runtime package was not found. Either set the PublishTrimmed property to...

@JamesNK can we just disable trimming for `netstandard2.1` targets?

> Trimming happens when publishing an app. Who is publishing? This error happens very early on, during framework reference resolution. Presumably the SDK is doing some scanning that sees we...