mtimbs

{
  "compilerOptions": {
    // project options
    "lib": [
      "ESNext",
      "dom"
    ], // specifies which default set of type definitions to use ("DOM", "ES6", etc)
    "outDir": "lib", // .js (as well as .d.ts, .js.map, etc.) files will be emitted into this directory.,
    "removeComments": true, // Strips all comments from TypeScript files when converting into JavaScript- you rarely read compiled code so this saves space
    "target": "ES6", // Target environment. Most modern browsers support ES6, but you may want to set it to newer or older. (defaults to ES3)

bradtraversy

MongoDB Cheat Sheet

Show All Databases

show dbs

Show Current Database

delibytes

React & JSX Cheatsheet

Overview
JSX HTML	<div>...</div>
JSX Component	<Component property={javascript} /> <Component property='string' />
JSX Component with Children	<Component>{children}</Component> reference: props.children
Escaping JavaScript	{...}
require statements	const React = require('react'); const ReactDOM = require('react-dom');
npm modules	react, react-dom

jareware

⇐ back to the gist-blog at jrw.fi

Advanced SCSS

Or, 16 cool things you may not have known your stylesheets could do. I'd rather have kept it to a nice round number like 10, but they just kept coming. Sorry.

I've been using SCSS/SASS for most of my styling work since 2009, and I'm a huge fan of Compass (by the great @chriseppstein). It really helped many of us through the darkest cross-browser crap. Even though browsers are increasingly playing nice with CSS, another problem has become very topical: managing the complexity in stylesheets as our in-browser apps get larger and larger. SCSS is an indispensable tool for dealing with this.

This isn't an introduction to the language by a long shot; many things probably won't make sense unless you have some SCSS under your belt already. That said, if you're not yet comfy with the basics, check out the aweso