Javascript

https://stackoverflow.blog/2019/09/12/practical-ways-to-write-better-javascript/

https://twitter.com/wesbos/status/1238468738946646017

Optional Chaining (deep property checking) is now in Chrome, Firefox and babel-preset-env 7.8.0.
This is a huge improvement in checking if nested properties exist!

SCHEDULED: [2022-03-25]

http://www.datejs.com/ looks ok, supports fuzzy stuff like 'next week', 'previous month', etc

https://medium.com/@binyamin/enabling-async-await-and-generator-functions-in-babel-node-and-express-71e941b183e2

Uncaught ReferenceError: regeneratorRuntime is not defined
I found this answer to my troubles and it worked when I implemented it. Just change .babelrc to the following:
{
  "presets": [
    [
      "@babel/preset-env",
      {
        "targets": {
          "node": "10"
        }
      }
    ],
    "@babel/preset-react"
  ]
}

https://stackoverflow.com/questions/42183155/is-it-safe-to-use-async-await-now

So depending on what you think is acceptable it is either safe or not safe. Note the following:
    This question was originally asked on 2017, and we have come a long way so async/await is much more safe to use now.
    By 2019, most mobile devices already support async/await.
    Node 8 is released on May 2017 so it should be safe to use async/await on Node.js unless your Node.js servers are very outdated.

Points for the worker without an external file. That's one cool trick

https://news.ycombinator.com/item?id=22534639

https://www.reddit.com/r/reactjs/comments/7z87o9/implementing_infinite_scrolling/

ssuming its only 100 items, i'd just display them all from the start, and let scroll do what scroll does. if you're trying to simplify a real world example where you might have 1000's of initially returned items, then something similar to /u/pqnst but instead of just slicing 0,(page * 20), you'd have to slice(20 * (page - 1), 20 * page) and account for the height of the sliced out elements in the scrollTop of the scrolling container

https://stackoverflow.com/questions/24641592/injecting-iframe-into-page-with-restrictive-content-security-policy

Periodic reminder that `await import('//dev.jspm.io/[pkg]')` allows you to import anything from npm in the browser instantly. I often use this in the console to test things out.

https://twitter.com/guybedford/status/1202022281633030145

https://github.com/stidges/jquery-searchable

Tiny, fast jQuery plugin to search through elements as you type.

https://www.npmjs.com/package/flexsearch

https://svelte.dev/blog/svelte-3-rethinking-reactivity

Svelte is a component framework — like React or Vue — but with an important difference. Traditional frameworks allow you to write declarative state-driven code, but there's a penalty: the browser must do extra work to convert those declarative structures into DOM operations, using techniques like
that eat into your frame budget and tax the garbage collector.
Instead, Svelte runs at build time, converting your components into highly efficient imperative code that surgically updates the DOM. As a result, you're able to write ambitious applications with excellent performance characteristics.

By using list.children instead of list.childNodes, you can avoid the check for text nodes.

A bit more minified/modern version of this that I'm using:
    function $e(t='div',p={},c=[]){
      let el=document.createElement(t);
      Object.assign(el,p);
      el.append(...c);
      return el;
    }
    var $t=document.createTextNode.bind(document);

https://lobste.rs/s/u2dyrr/small_trick_on_using_console_log_print

console.log("User(%o)", user)
console.table is also useful
    faitswulff avatar faitswulff 3 hours ago | link |
I’ve started to use console.table for pretty much everything. It’s so nice.

Tried out DenoJS to play around with Vue and it was very pleasant to use.
I'm going to have to read more into it, but I think any personal JS projects will be using Deno simply due to the lack of dependencies and speed.

https://htmldom.dev/

let util = require('util')
console.log(util.inspect(resp, {showHidden: false, depth: 1}))

https://github.com/antonmedv/codejar

CodeJar honey_pot can be used via modules:
<script type="module">
  import {CodeJar} from 'https://medv.io/codejar/codejar.js'
</script>

Having used both (Flow for one very large project and TypeScript for a few less large projects) I am very much in the TypeScript camp now.

Firstly, DefinitelyTyped has vastly more library defs available than flow-typed, which matters a whole lot more than you might realize. It's pretty rare that `npm install @types/name-of-package` comes up empty.

Secondly, Flow feels slower and buggier; I use VS Code full-time and have found that TS reacts to code changes far more quickly and accurately than Flow (almost instantaneously across an entire project), and provides much more useful error messages (I lost count of the number of times I saw `merge_strict_job exception: Utils_js.Key_not_found("LeaderHeap")`, which I believe usually indicates a bug in Flow itself but is also completely useless and extremely difficult to debug). Of course I realize that TS and Code are both Microsoft products so it's not surprising that TS works better, but even in Atom with Nuclide I found that Flow was a bit slow to catch up to things, and still sometimes threw very cryptic errors.

Finally, TS has a pretty solid built-in compiler which tracks the official spec, and natively supports features like `async`/`await`.

To your original question, I'm currently working on a React-heavy project with TS and have found it to have excellent support. Flow works very well with React as well, which is to be expected since both come from Facebook. I think either would be a fine decision, but definitely feel TS has the edge in stability and speed.

https://www.reddit.com/r/javascript/comments/ad6zoj/npm_vs_yarn_which_one_and_why/

npm has greatly improved since the original days of yarn. With lock files and better dependency tree management, I find very few reasons to use yarn nowadays.
I'd say use npm until you find a feature from yarn that requires you to switch. npm is included with every Node.js install.

https://github.com/addyosmani/es6-tools#readme

https://stackoverflow.com/questions/10471759/inserting-large-quantities-in-indexeddbs-objectstore-blocks-ui

Jest is amazing! It is out of the box , takes way less time to run the tests than mocha. A small side note: If you're using a vue js app, you are going to want to take a look at [Vue Test Utils](https://vue-test-utils.vuejs.org/). Makes life so much easier. Also sinon.js for spies and fakes. PM me if you need tips and tricks to start with automated testing. 

https://www.pluralsight.com/guides/javascript-callbacks-variable-scope-problem

ECMAScript 6 introduces the let keyword which allows you to declare a variable scoped to the nearest enclosing block and not global like var does. Thus the closure problem can be solved simply by replacing var with let:

https://twitter.com/swyx/status/1208461215069945856

Rewrote my Twitter search from React to Svelte
@Reactjs  42kb
Code: https://github.com/sw-yx/bettertwitter/tree/reactapp
Site: https://inspiring-fermat.netlify.com

@Sveltejs 5kb
Code: https://github.com/sw-yx/bettertwitter/tree/master
Site: https://bettertwitter.netlify.com
Had trouble w/ eslint/prettier, but overall much less code to write

https://gridjs.io/?hn

https://datagridxl.com

• console.group() and console.groupEnd()
  

Creates a new inline group, indenting all following output by another level. To move back out a level, call groupEnd().

• console.time() and console.timeEnd()
  

console.time() – Starts a timer with a name specified as an input parameter. Up to 10,000 simultaneous timers can run on a given page.
console.timeEnd() – Stops the specified timer and logs the elapsed time in seconds since it started.