Skip to content
🔜
working on that thing you asked about
🔜
working on that thing you asked about
GitHub Sponsor
Block or report user

Report or block ljharb

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
Block or report user

Report or block ljharb

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse

Pinned

  1. JavaScript Style Guide

    JavaScript 87.2k 16.7k

  2. Node Version Manager - Simple bash script to manage multiple active node.js versions

    Shell 36k 3.4k

  3. ECMAScript 5 compatibility shims for legacy (and modern) JavaScript engines

    JavaScript 6.7k 909

  4. A querystring parser with nesting support

    JavaScript 4.3k 368

  5. Tracking ECMAScript Proposals

    8.1k 301

  6. 1
    While attempting to explain JavaScript's `reduce` method on arrays, conceptually, I came up with the following - hopefully it's helpful; happy to tweak it if anyone has suggestions.
    2
    
                  
    3
    ## Intro
    4
    JavaScript Arrays have lots of built in methods on their prototype. Some of them *mutate* - ie, they change the underlying array in-place. Luckily, most of them do not - they instead return an entirely distinct array. Since arrays are conceptually a contiguous list of items, it helps code clarity and maintainability a lot to be able to operate on them in a "functional" way. (I'll also insist on referring to an array as a "list" - although in some languages, `List` is a native data type, in JS and this post, I'm referring to the concept. Everywhere I use the word "list" you can assume I'm talking about a JS Array) This means, to perform a single operation on the list as a whole ("atomically"), and to return a *new* list - thus making it much simpler to think about both the old list and the new one, what they contain, and what happened during the operation.
    5
    
                  

Contribution activity

July 2019

Created a pull request in benmosher/eslint-plugin-import that received 8 comments

[Refactor] use native JS instead of lodash

This removes a large dep that often has CVEs, in exchange for using native JS which is clearer and more maintainable. Closes #1224.

+30 −31 8 comments
10 repositories not shown

Created an issue in tc39/proposal-nullish-coalescing that received 10 comments

pre-Stage 3 review

(you'll also need signoff from the designated reviewers, and from @zenparsing) I wonder if maybe "NullishExpression" should be "NullishORExpressio…

10 comments
9 contributions in private repositories Jul 2 – Jul 16

Seeing something unexpected? Take a look at the GitHub profile guide.

You can’t perform that action at this time.