Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WinterCG Minimum Common Web Platform API Alignment #10297

Open
11 of 42 tasks
NathanWalker opened this issue May 25, 2023 · 3 comments
Open
11 of 42 tasks

WinterCG Minimum Common Web Platform API Alignment #10297

NathanWalker opened this issue May 25, 2023 · 3 comments
Assignees
Milestone

Comments

@NathanWalker
Copy link
Contributor

NathanWalker commented May 25, 2023

Is your feature request related to a problem? Please describe.

In addition to what the NativeScript runtimes provide, they should also provide all the common interfaces and global objects expected from any state of the art JavaScript runtime. WinterCG is a community group doing excellent work in this space to help runtime interoperability of APIs across runtimes.

Describe the solution you'd like

Ensure compliance with at least the minimum specification:

Interfaces:

Global methods / properties:

globalThis

Please accept these terms

@NathanWalker NathanWalker added feature-pending-triage A new feature request pending triage to confirm validity. in progress and removed feature-pending-triage A new feature request pending triage to confirm validity. labels May 25, 2023
@NathanWalker NathanWalker added this to the 9.0 milestone May 25, 2023
@NathanWalker NathanWalker pinned this issue Jan 9, 2024
@MrSnoozles
Copy link

MrSnoozles commented Feb 24, 2024

@NathanWalker I needed queueMicrotask for the latest Vue Apollo Client to work. I polyfilled it using

import queueMicrotask from "queue-microtask";
global.queueMicrotask ??= queueMicrotask;

which works perfectly. The queue-microtask library is effectively 5 lines of code, so that could be added easily as well.

@dangrima90
Copy link

dangrima90 commented Feb 26, 2024

@NathanWalker I've a question about the polyfills that will be eventually implemented. I see that in the list above there's no mention of Intl API. My main point of interest is the NumberFormat class, as currently to support number formatting via .toLocaleString(), or be to able to use formatToParts(), polyfills have to be used (such as format js polyfills).

Is this something out of scope for this update please?

@rigor789 rigor789 unpinned this issue Mar 8, 2024
@NathanWalker
Copy link
Contributor Author

@dangrima90 Intl will be an optional package you could include when your app needs it vs. being built into runtime by default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants
@NathanWalker @rigor789 @edusperoni @triniwiz @MrSnoozles @dangrima90 and others