[release/7.0] [wasm] Catch error from loading "node:crypto" module #79351
Conversation
* Catch error from loading node:crypto module. * Throw error with explanation when crypto module is not available. * Fix providing error throwing polyfill.
maraf
added
Servicing-consider
|
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsBackport of #78916 to release/7.0 Customer ImpactBased on node documentation, there might be a build of node without "node:crypto". In such case the module import will throw an exception. In #78696 we load "node:crypto" module during the runtime startup and this PR we are catching such exception and rethrow it only when user tries to use the API. It restores the behavior before #78696 when crypto API is not available. TestingManual RiskNone IMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.
|
marek-safar
added
Servicing-approved
|
I accidentally pressed Close instead of Squash+Merge. I will resubmit this backport PR and merge it. Apologies. |
ghost
locked as resolved and limited conversation to collaborators
Backport of #78916 to release/7.0
Customer Impact
Based on node documentation, there might be a build of node without "node:crypto". In such a case the module import will throw an exception. In #78696 (backport #78766) we load "node:crypto" module during the runtime startup and in this PR we are catching such exception and rethrowing it only when user tries to use the API.
It restores the behavior before #78696 when crypto API is not available.
It should be included in the same release as #78696 (backport #78766).
Testing
Manual
Risk
None
IMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.