webpack-common-shake
proposal-do-expressions
Our great sponsors
webpack-common-shake | proposal-do-expressions | |
---|---|---|
2 | 19 | |
914 | 1,066 | |
- | 2.3% | |
0.0 | 0.0 | |
about 1 year ago | about 3 years ago | |
JavaScript | HTML | |
- | MIT License |
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-do-expressions
-
TypeScript Is Surprisingly OK for Compilers
> no pattern matching/switch expressions
They're still waiting on the do expression proposal for that (https://github.com/tc39/proposal-do-expressions), which has been in the bikeshedding stage for the past five years.
-
[AskJS] Opinions on using self executing functions as multi-line expressions.
At some point, it may be superseded by do blocks, but for now it's really your best bet.
-
What is this called? { id ? <Dashboard/> : <Login/> } and can I make it check for multiple things like a switch case?
But there is a proposal for do-expression : https://github.com/tc39/proposal-do-expressions
-
Using {Blocks} in Rust & Go for Fun & Profit
It's also the reason why do expressions are my most anticipated feature for JS.
-
Pipe Operator (|>) For JavaScript
> They should repurpose `do` so that `do {}` (without the `while`) is an expression that you can put statements inside and return the last statement.
There's a proposal for precisely that. Unfortunately, only Stage 1 though.
https://github.com/tc39/proposal-do-expressions
- Is a single ternary operator inside the returned JSX acceptable?
-
[AskJS] Is there ever a good use for loose blocks in JS?
It's one of the main reasons why I really want the do-expression propsal to work out, because then it would become:
- The TC39 Process
-
[AskJS] What are still present issues in contemporary (2022) JavaScript?
Do blocks. Okay, this is actually a proposal so maybe someday. Basically blocks that can resolve to an expression.
-
'The best thing we can do today to JavaScript is to retire it,' says JSON creator Douglas Crockford • DEVCLASS
Tomorrow, do expressions:
What are some alternatives?
proposal-upsert - ECMAScript Proposal, specs, and reference implementation for Map.prototype.upsert
captureSystemAudio - Capture system audio ("What-U-Hear")
meta - Meta discussions and unicorns. Not necessarily in that order.
native-messaging-bash - Bash Native Messaging host.
esm - Tomorrow's ECMAScript modules today!
proposal-pipeline-operator - A proposal for adding a useful pipe operator to JavaScript.
loader - A universal async JS loader.
node-fetch - A light-weight module that brings the Fetch API to Node.js
caya - a tiny useful simple language experiment
node - Node.js JavaScript runtime ✨🐢🚀✨
coffeescript - Unfancy JavaScript