-
-
Notifications
You must be signed in to change notification settings - Fork 37.2k
Workaround to prevent ICU trouble #30544
Copy link
Copy link
Closed
Labels
i18n-apiIssues and PRs related to Node.js internationalization support.Issues and PRs related to Node.js internationalization support.wasmIssues and PRs related to WebAssembly.Issues and PRs related to WebAssembly.
Description
Activity
Metadata
Metadata
Assignees
Labels
i18n-apiIssues and PRs related to Node.js internationalization support.Issues and PRs related to Node.js internationalization support.wasmIssues and PRs related to WebAssembly.Issues and PRs related to WebAssembly.
My current workaround is to build and run the icu packages with wasm “https://www.npmjs.com/package/wasm-intl” which gives the application developer full control of this ICU back. But raises the question if ICU should shipped with node in future version as native or wasm compilation which enables that node could use architecture independent translation sets that give the application dev controllback and not raises these kind of problems at all.
I knew that future version of node will ship the full-icu in standard configuration. But why not use this case to explore wasm in node core.