tc39 / proposal-string-cooked

ECMAScript proposal for String.cooked built-in template tag

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Polyfill

jamiebuilds opened this issue · comments

I found writing a polyfill to be a useful tool for discussions.

This polyfill can live in this repository for simplicity, and shouldn't be published (others will publish polyfills).

It should also be as pedantic as possible, being explicit about matching the entirety of the spec.

(in case polyfill authors make their way here: also, polyfills shouldn't BE published or used in production prior to stage 3)

If you want the in-repo polyfill to have running code, you can also use https://npmjs.com/es-abstract so it maximally matches the spec text.

Off-topic: I really hope we could have an official process of such polyfills (experimental features).

zloirock/core-js#990

Waiting for the TC39 discussion and stabilization.

If you want the in-repo polyfill to have running code, you can also use npmjs.com/es-abstract so it maximally matches the spec text.

After issues like this that are not fixed for many years, I don't think that makes sense to recommend it to third-party polyfills authors.

Let's keep this issue on topic, I don't want to have a huge meta conversation about process here