fix(@angular-devkit/build-angular): Sass compilation in StackBlitz webcontainers

[alan-agius4]

When process.versions.webcontainer is a string it means that we are running in a StackBlitz webcontainer. SassWorkerImplementation uses receiveMessageOnPort Node.js worker_thread API to ensure sync behavior which is ~2x faster. However, it is non trivial to support this in a webcontainer and while slower we choose to use dart-sass which in Webpack uses the slower async path.

// cc @markwhitfeld

[markwhitfeld]

That check looks good 👍

[d3lm]

Thanks so much for this quick implementation and for adding an env check here for the time being. I am actually gonna look into this very soon so we can support receiveMessageOnPort at least minimally. Thanks a lot!

[dgp1130]

Just for context, do we only use dart-sass for webcontainers, or are there other usages were it is still supported? I'm just wondering if this is the major thing blocking us from moving to node-sass, or if there are other problems that need to be resolved anyways?

[alan-agius4]

Just for context, do we only use dart-sass for webcontainers, or are there other usages were it is still supported? I'm just wondering if this is the major thing blocking us from moving to node-sass, or if there are other problems that need to be resolved anyways.

We only support dart-sass.

[dgp1130]

We only support dart-sass.

Ah thanks, I was getting the direction of node-sass -> dart-sass backwards, and thought this might be related. Disabling the worker in webcontainers is reasonable until it has the necessary support.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}