proposal-built-in-modules
proposal-built-in-modules copied to clipboard
tc39
These are some fundamental questions I've heard from folks when I discuss built-in modules with JavaScript developers. Have you heard these concerns, or any other concerns that aren't tracked in...
The explainer in this repository has version numbers. The Web, ~~Node~~ and JS built-ins are generally unversioned, so far. What are the advantages and disadvantages of versioning? How should it...
Functional patterns in JavaScript are COOOOL. Depending on whether proposals such as [these](https://github.com/tc39/proposal-pipeline-operator/wiki) get approved, it might be a good idea to boil more fp into a standard library. Aka:...
Since we already have precedent of global objects, we would now be introducing a dichotomy: some standard library functionality is available in globals, and other standard library functionality is available...
Normal JS modules only execute their top-level statements if someone imports them. In this proposal, if you want to polyfill built-in modules, you have to call `BuiltinModule.export` eagerly, just in...
It must have a new syntax so it can be statically analyzed. Here is an example (I know it is conflicting with TypeScript syntax though) ```js declare module "std:Complex" {...
Governance
Based on the readme, we identified that some of our concerns are still outstanding: https://github.com/mozilla/standards-positions/issues/147#issuecomment-513274020 The constraint that we would introduce here is that it is not only TC39 which...
Here are what I understand as the reasons why the champions feel built-in modules should exist: 1. *Performance:* Global objects increase code size and memory usage. Built-in modules give implementations...
It would help to hear some of the motiviations for the global, and why these could not be adequately replaced with treating the BuiltinModule object as a builtin module itself....
