swyxio

// please check https://docs.netlify.com/configure-builds/environment-variables/#declare-variables for most up to date info
// this was created before those docs existed

process.env = {
  /**
   * 
   * AUTOMATICALLY SET BY NETLIFY. IMMUTABLE!
   * docs: https://www.netlify.com/docs/continuous-deployment/#environment-variables
   * 
   */

kentcdodds

Code Coverage

Code coverage is accomplished with Jest thanks to babel-plugin-istanbul. It transforms your code to "instrument" it for coverage. When your tests are finished, Jest reads the coverage data to generate the coverage report.

Reviewing code that has been instrumented for coverage can help understanding how coverage works and how to interpret coverage reports.

sebmarkbage

I heard some points of criticism to how React deals with reactivity and it's focus on "purity". It's interesting because there are really two approaches evolving. There's a mutable + change tracking approach and there's an immutability + referential equality testing approach. It's difficult to mix and match them when you build new features on top. So that's why React has been pushing a bit harder on immutability lately to be able to build on top of it. Both have various tradeoffs but others are doing good research in other areas, so we've decided to focus on this direction and see where it leads us.

I did want to address a few points that I didn't see get enough consideration around the tradeoffs. So here's a small brain dump.

"Compiled output results in smaller apps" - E.g. Svelte apps start smaller but the compiler output is 3-4x larger per component than the equivalent VDOM approach. This is mostly due to the code that is usually shared in the VDOM "VM" needs to be inlined into each component. The tr

kentcdodds

const {createJestRunner} = require('create-jest-runner')

module.exports = createJestRunner(require.resolve('./node-runner'))

kentcdodds

{
  "name": "workshop-computer-validator",
  "version": "1.0.0",
  "description": "I use this to validate people's computers have the proper versions of node and npm installed for a workshop",
  "bin": "./validate-system.js",
  "dependencies": {
    "semver": "7.1.3"
  }
}

kentcdodds

#!/usr/bin/env node

const path = require('path')
const inquirer = require('inquirer')
const replace = require('replace-in-file')
const isCI = require('is-ci')
const spawn = require('cross-spawn')

const fileGlob = process.argv[2] || 'src/**/*.*'
const files = path.isAbsolute(fileGlob)

kentcdodds

{
  "name": "workshop-setup",
  "version": "1.0.0",
  "description": "This is the common setup script for most of my workshops",
  "bin": "./setup.js"
}

kentcdodds

#!/usr/bin/env node

const path = require('path')
const fs = require('fs')
const glob = require('glob')
const pkg = require(path.join(process.cwd(), 'package.json'))
const {title: projectTitle, homepage: projectHomepage} = pkg

// update production deploy links
glob.sync('src/**/*.md').forEach(filepath => {

kentcdodds

#!/usr/bin/env node

const path = require('path')
const fs = require('fs')
const glob = require('glob')
const projectTitle = require(path.join(process.cwd(), 'package.json')).title

const linkRegex = /https?:\/\/ws\.kcd\.im.*?$/m

const titleRegex = {

kentcdodds

const Discord = require('discord.js')

// your bot token
const token = 'NzM4MDk2NjA4NDQwNDgzODcw.XyG8CA.RbwIBFnAbrRDYOlTdLYgG_T4CMk'
const discordUsername = 'example#1234'
const roleToAdd = 'Cool Person'
const guildName = 'Your Guild Name'

function deferred() {
  let resolve, reject