webpack-common-shake
proposal-record-tuple
webpack-common-shake | proposal-record-tuple | |
---|---|---|
2 | 73 | |
914 | 2,423 | |
- | 0.9% | |
0.0 | 2.7 | |
about 1 year ago | 5 months ago | |
JavaScript | HTML | |
- | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
webpack-common-shake
-
CommonJS Is Hurting JavaScript
While I agree the dynamic nature of CommonJS would be problematic, there were successful projects around treeshaking commonjs[0] that worked really well.
I think dynamic imports have some of the same footguns here, to be honest. Can't deny ESM is easier to statically analyze though, that much appears to be true across the board based on available evidence.
[0]: https://github.com/indutny/webpack-common-shake
-
[AskJS] What are still present issues in contemporary (2022) JavaScript?
Tree shaking in CommonJS is possible: here's a Webpack CommonJS Tree Shaking package.
proposal-record-tuple
-
Union, intersection, difference, and more are coming to JavaScript Sets
relevant issue, which is at the crux of this problem: https://github.com/tc39/proposal-record-tuple/issues/387
-
The Everything NPM Package
There are still so many basic things that aren't in the JS stdlib, though. A good example is Map - if you need to use a tuple of two values as a key, you're SOL because there's no way to customize key comparisons. Hopefully we'll get https://tc39.es/proposal-record-tuple/ eventually, but meanwhile languages ranging from C++ to Java to Python have had some sensible way to do this for over 20 years now.
-
Deep Cloning Objects in JavaScript, the Modern Way
If you’re reaching for structuredClone, what you really want is native immutable Record and Tuple syntax, and the companion “deep path properties” syntax which allows for efficient and ergonomic immutable updates:
- https://github.com/tc39/proposal-record-tuple
-
Cool language features that Rust is missing?
It will be called "record" in JavaScript which will swing the popularity back the other way I guess (currently a language proposal)
-
Why doesn't TypeScript properly type Object.keys?
I suspect considering the strong desire to maintain consistency with JavaScript, we will eventually see something that when the Record proposal passes through tc39
-
ES2023 features list!
I hope the Record and Tuple proposal makes it through
-
ES2023 introduces new array copying methods to JavaScript
I mean, I'd love some real immutable/persistent data structures in JS by default, or even some Immer-like syntax sugar. Something like the record/tuple proposal would be awesome.
-
What's new in ECMAScript 2023
This will become very useful once Records and Tuples are a thing, because it allows you to store object references in a record/tuple (which by definition can only contain primitives).
-
[AskJS] Is JavaScript missing some built-in methods?
Record and tuple is at stage 2
-
The huge potential of Kotlin/Wasm
Also, js has an ongoing immutable value data types proposal.
What are some alternatives?
proposal-upsert - ECMAScript Proposal, specs, and reference implementation for Map.prototype.upsert
zod - TypeScript-first schema validation with static type inference
meta - Meta discussions and unicorns. Not necessarily in that order.
Immer - Create the next immutable state by mutating the current one
esm - Tomorrow's ECMAScript modules today!
typescript-eslint - :sparkles: Monorepo for all the tooling which enables ESLint to support TypeScript
loader - A universal async JS loader.
typescript-is
proposal-do-expressions - Proposal for `do` expressions
TypeScript - TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
node-fetch - A light-weight module that brings the Fetch API to Node.js
proposals - Tracking ECMAScript Proposals