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 90.4k 17.5k

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

    Shell 38.1k 3.6k

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

    JavaScript 6.8k 918

  4. A querystring parser with nesting support

    JavaScript 4.7k 424

  5. Tracking ECMAScript Proposals

    9.1k 342

  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

November 2019

Created a pull request in npm/cli that received 1 comment

unsupported: npm v6.10.0 breaks on node v6.0, v6.1, v9.0 - v9.2

nvm-sh/nvm@100861d npm v6.10 caused npm to no longer work on node v6.0, v6.1, v9.0, v9.1, and v9.2. This PR isn't to debate semver adherence, thoug…

+1 −1 1 comment
1 contribution in private repositories Nov 5

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

You can’t perform that action at this time.