| import * as IOEffects from 'redux-saga/effects' | |
| export function * select (...args) { | |
| return yield IOEffects.select(...args) | |
| } | |
| export function * put (...args) { | |
| return yield IOEffects.put(...args) | |
| } |
When Babel 6 came out, it was hard for a lot of packages to upgrade because it was essentially an entirely different category of thing than Babel 5. So what happened was that some packages upgraded, and some didn't — at least not straight away.
Some projects took the prima facie enlightened view that packages should expose untranspiled code, so that the consumers of that code could determine for themselves what needed to get transpiled based on the environments they supported.
That was a costly decision. If I was the author of an app that was using Babel 6, I couldn't import a library that was still using Babel 5 and shipping untranspiled code (because the configs were completely incompatible), and vice versa. Frankly, it was a bloody nuisance. We are bad at anticipating these sorts of issues. It will happen again at some point.
Adding a few extra bytes to pkg.main or pkg.module is a small price to pay for things just working. As well as avoiding the aforementioned headaches, it means that your
| (require 'dash) | |
| (require 's) | |
| (require 'loop) | |
| (require 'icons-in-terminal) | |
| (defun my-char-at-point (&optional p) | |
| "P." | |
| (let ((point (or p (point)))) | |
| (if (< point (point-max)) (buffer-substring-no-properties point (1+ point)) | |
| ""))) |
| // make sure to have babel-plugin-preval setup so this import works as expected | |
| // https://github.com/kentcdodds/babel-plugin-preval | |
| import docs from "./get-react-docs.js" | |
| // do whatever you want with all of the component documentation | |
| function renderDocs() { | |
| return ( | |
| <div> | |
| {docs.map(doc => ...)} | |
| </div> |
| /** | |
| * Shared interfaces between the modules 'redux-saga' and | |
| * 'redux-saga/effects' | |
| */ | |
| declare interface $npm$ReduxSaga$Channel { | |
| take: (cb: (msg: mixed) => void) => void, | |
| put: (msg: mixed) => void, | |
| close: Function, | |
| } |
Last updated March 13, 2024
This Gist explains how to sign commits using gpg in a step-by-step fashion. Previously, krypt.co was heavily mentioned, but I've only recently learned they were acquired by Akamai and no longer update their previous free products. Those mentions have been removed.
Additionally, 1Password now supports signing Git commits with SSH keys and makes it pretty easy-plus you can easily configure Git Tower to use it for both signing and ssh.
For using a GUI-based GIT tool such as Tower or Github Desktop, follow the steps here for signing your commits with GPG.
This is based on a guide on the Ubnt forums.
Log into your Edgerouter and run the following - sudo -i && vi /config/user-data/update-adblock-dnsmasq.sh
This will switch you to the root user and open up vi.
#!/bin/bash
| import React from 'react'; | |
| import PropTypes from 'prop-types' | |
| import debounce from 'lodash.debounce' // or whatevs | |
| import isEqual from 'lodash.isEqual' | |
| class AutoSave extends React.Component { | |
| static contextTypes = { | |
| formik: PropTypes.object | |
| } |
| #!/bin/sh | |
| # some parts of this forked from https://github.com/blended/sketch-collaboration | |
| # cf. https://github.com/chadlavi/sketch-collaboration | |
| if [ ! `command -v jq` ]; then | |
| echo "you need to install jq. If you use Homebrew, try 'brew install jq'" | |
| exit 1 | |
| fi | |
| if [ -z "$1 ]; then |