babel-plugin-lodash
proposal-pipeline-operator
babel-plugin-lodash | proposal-pipeline-operator | |
---|---|---|
3 | 105 | |
1,957 | 7,507 | |
- | 0.6% | |
0.0 | 2.7 | |
about 1 year ago | 10 months ago | |
JavaScript | HTML | |
GNU General Public License v3.0 or later | BSD 3-clause "New" or "Revised" 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.
babel-plugin-lodash
- Webpack tree shaking not working as I expected
-
Let's talk about Lodash
Alternatively, there is a Babel plugin that can do this for you. There is also a webpack plugin that will further optimize things.
-
Minimizing Webpack bundle size
Similar to babel-plugin-import, the babel-plugin-lodash plugin cherry picks the code we need to import from lodash. The parsed size of the entire lodash package is ~600KB, so we definitely don’t want everything.
proposal-pipeline-operator
-
Russ Cox is stepping down as the Go tech lead
> The reluctancy to introduce new syntax too quickly (looking at you, TC39 and Babel) makes go an almost maintenance free language.
Could you provide some examples of this? From knowledge of the pipeline operator proposal[0], moving fast and breaking things isn't always a priority.
[0]: https://github.com/tc39/proposal-pipeline-operator/commit/da...
- Brief history of the JavaScript pipe operator
-
The long path of JavaScript - from ES6 until today.
The pipeline operator proposal, which is currently in Stage 2, introduces a new operator |> that allows developers to chain multiple function calls together in a more readable and concise way. Together with the pipeline operator, the placeholder operator % is being introduced which will hold the previous function’s value. It should enhance the readability and maintainability of code, especially when performing a series of operations on a value.
-
Pipeline Operator great again!
Current Status: You'd have to check the TC39 proposals repository or the official proposal text for the most recent status. As of my last update, it had not yet reached Stage 4 (final stage) of the TC39 process, which means it wasn't part of the ECMAScript specification yet.
-
pipesAreFun
Javascript may get it https://github.com/tc39/proposal-pipeline-operator https://youtu.be/dQw4w9WgXcQ
-
JavaScript Gom Jabbar
It can be further simplified. For example, you don't need two separate functions to extract the first chat completion message etc.
This version:
- uses existing language constructs
- can be immediately understood even by the most junior devs
- is likely to be 1000 times faster
- does not rely on an external dependency that currently has 143 issues and every two weeks releases a new version adding dozens of new methods to things
Note: one thing I do wish Javascript adopted is pipes: https://github.com/tc39/proposal-pipeline-operator
-
What's new in ES2023?
Still in stage 2 atm https://github.com/tc39/proposal-pipeline-operator
- lizod - spiritual successor of zod less than 1kb
- Updates from the 96th TC39 meeting
-
Mostly adequate guide to FP (in JavaScript)
Both are active tc39 proposals :)
https://github.com/tc39/proposal-pipeline-operator - Stage 2
https://github.com/tc39/proposal-pattern-matching - Stage 1
Hopefully we get both in the next couple of years.