[drenvuk]

This is pretty disgusting to me. It just looks messy.

    const testPlus = () => {
       assert.equal(3+4, 7);
    } |> Object.assign(%, {
        name: 'Test the plus operator',
    });

The previous code is equivalent to:

    const testPlus = () => {
      assert.equal(3+4, 7);
    }
    Object.assign(testPlus, {
      name: 'Testing +',
    });

We could also have used the pipe operator like this:

    const testPlus = () => {
      assert.equal(3+4, 7);
    }
    |> (%.name = 'Test the plus operator', %)
    ;

I don't really see the point in general purpose chaining. I don't really see the point of flatmapping tons of nested function calls. Instead we can abstract it and start another nested stack if necessary. I thought we moved away from utilizing promises towards async await because of the chaining issue. It feels like it's being repeated.

The example from TC39 is also fairly insipid:

    console.log(
      chalk.dim(
        `$ ${Object.keys(envars)
          .map(envar =>
            `${envar}=${envars[envar]}`)
          .join(' ')
        }`,
        'node',
        args.join(' ')));

I don't think it should have been written like that. The Object.keys().map().join() should've been assigned to an appropriately named variable before being used in another function. There are better ways to avoid writing code this way.