The Wayback Machine - https://web.archive.org/web/20200530024130/https://github.com/ljharb
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

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse

Sponsors

@StandardResumeSponsors @AdrienGiboire @maraisr @dshaw @OussamaRomdhane @Jtalk @shawnharmsen @smcelhinney @6ewis @wuweiweiwu @infomofo @chrisJohn404 @chidimo

Sponsoring

@eslint @PeterDaveHello @tatianamac @sdras @vaidehijoshi @nzakas @gr2m @lynncyrin @zkat @hzoo
Block or report user

Report or block ljharb

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse

Pinned

  1. JavaScript Style Guide

    JavaScript 96.3k 18.7k

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

    Shell 42.1k 4.1k

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

    JavaScript 6.9k 937

  4. A querystring parser with nesting support

    JavaScript 5.3k 481

  5. Tracking ECMAScript Proposals

    10.9k 427

  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

May 2020

Created a pull request in tc39/ecma262 that received 8 comments

Editorial: make `NumberBitwiseOp`, `BigIntBitwiseOp`, `ByteListBitwiseOp` consistent

Ensure op is a String in all cases, and ensure all three operations assert on the contents of op. Previously, NumberBitwiseOp and ByteListBitwiseOp

+17 −15 8 comments
29 repositories not shown

Created an issue in tabatkins/proposal-item-method that received 4 comments

Question about subclass claim in the readme

However, that would mean the values aren't of type Array; various type-checking methods in the community looking for an Array would fail. Which m…

4 comments

Joined the pkgjs organization

@pkgjs
pkgjs

Tools for package maintainers by package maintainers

5 contributions in private repositories May 7 – May 28
You can’t perform that action at this time.