record-tuple-polyfill
record-tuple-polyfill copied to clipboard
bloomberg
A polyfill for the ECMAScript Record and Tuple proposal.
Signed-off-by: Richard Button made some minor tweaks to build config to get rid of some downleveling that breaks the polyfill.
Bumps [terser](https://github.com/terser/terser) from 5.12.1 to 5.14.2. Changelog Sourced from terser's changelog. v5.14.2 Security fix for RegExps that should not be evaluated (regexp DDOS) Source maps improvements (#1211) Performance improvements in...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
**Describe your changes** We provide to polyfill authors the tools to implement their own Babel plugin to inject polyfills (similarly to what Babel does with `core-js`): https://github.com/babel/babel-polyfills This is different...
**Describe the bug** It's `Record.fromEntries` argument type assertion issue, which is an array-like object for each item in its argument. **To Reproduce** ```js const record = Record.fromEntries([["a", 1], #["b", 2],...
Awesome work! **Is your feature request related to a problem? Please describe.** Is there ambitions to add typescript typings for this project? If so, I could maybe help you do...
I think it would be useful to enumerate spec violations and see which ones we can and can't fix over time.
It seems that the current implementation of updating a record is naive. For large records, the spread operator has bad performance. A possible improvement is to implement efficient persistent data...
To incorporate this bug fix https://github.com/babel/babel/issues/11926
The modules `@bloomberg/record-tuple-polyfill` and `@bloomberg/babel-plugin-proposal-record-tuple` are both published as private. You can verify by visiting either of these two links while signed out: - https://www.npmjs.com/package/@bloomberg/record-tuple-polyfill - https://www.npmjs.com/package/@bloomberg/babel-plugin-proposal-record-tuple I also noticed...
It could be helpful for practical usage to enable a version which is faster and less spec-compliant. It's not clear what the semantics should be exactly. This project is lower...