Please cover how it plans to evolve? That is, in two years l, imagine all current versions of modules supporting browsers have es2020 support, how do you tell preset-modules to stop transpiling es2020? Or should folks going back to preset-env in that case? Or something else?
-
-
-
Yep great q! Wrote down to talk about future and how to merge into preset-env (I think we mentioned it but actually doing it will take some work)
Kraj razgovora
Novi razgovor -
-
-
I'd like to understand the "right" package.json values for main/module/browser/etc. and how nomodule fits into that.
-
Yes, the missing piece of the puzzle for me is if the entry point for node & browsers isn’t the same
Kraj razgovora
Novi razgovor -
-
-
Probably already on your outline: transpiling node_modules
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
A plan for a faster core, like in Rust?
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Really interested in the idea of “un-transpiling” node_modules before transpiling to modern js.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
My big question: are the only solutions going to be tied to module/nomodule? We already want to produce >1 additional build for other support matrices, but most of the tooling progress seems focused on the nomodule pattern (we do a hacky UA sniffing approach currently).
- Još 2 druga odgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.