sindresorhus

Pure ESM package

The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.

This means you have the following choices:

1. Use ESM yourself. (preferred)
   Use import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.
2. If the package is used in an async context, you could use await import(…) from CommonJS instead of require(…).
3. Stay on the existing version of the package until you can move to ESM.

muffinista

#!/usr/bin/env ruby

#
# this code is modified from
#
# https://github.com/gingerbeardman/loveletter
#
# any mistakes are certainly added from me
#

NeuroWinter

FFMPEG '-i', file, '-c:v', 'libopenjpeg', "jpeg2000\\" + name + ".jp2"\

Convert image to jpeg2000
	ffmpeg -i in.png -c:v libopenjpeg out.jp2
	Hex Edit out.jp2
	ffmpeg -i in.jp2 -c:v png out.png

General Edit
ffmpeg -i input.avi -c:v mpeg2video -g 999 -q:v 1 output.avi
*edit in avidemux/whatever*

SuperPaintman

#!/bin/bash

#
# Author:       SuperPaintman <SuperPaintmanDeveloper@gmail.com>
# 

###
# Constants
###
RETVAL=0

mathiasbynens

Looking for support tables for HTML/CSS/JavaScript features or details on their implementation status in major browsers?

• Chrome Platform Status (covers Chromium and thus includes Opera)
• Firefox Platform Status
• Microsoft Edge Platform Status
• WebKit Feature Status
• API Catalog

And then there’s Can I use…?.

jackcarter

import requests
import time
import json

token = ''

#Delete files older than this:
ts_to = int(time.time()) - 30 * 24 * 60 * 60

def list_files():

paulirish

What forces layout / reflow

All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.

Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.

Element APIs

Getting box metrics

• elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent

tvlooy

#!/bin/bash

function test {
    MESSAGE=$1
    RECEIVED=$2
    EXPECTED=$3

    if [ "$RECEIVED" = "$EXPECTED" ]; then
        echo -e "\033[32m✔︎ Tested $MESSAGE"
    else

chantastic

Hi Nicholas,

I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:

The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't

yoavniran

The Ultimate Unit Testing Cheat-sheet

---

• Sinon Chai
• Chai
• Sinon