Since v8.1 (May 2018), Vim has shipped with a built-in terminal. See https://vimhelp.org/terminal.txt.html or type :help terminal for more info.
Why use this? Mainly because it saves you jumping to a separate terminal window. You can also use Vim commands to manipulate a shell session and easily transfer clipboard content between the terminal and files you're working on.
| https://jennamolby.com/how-to-use-cookies-to-capture-url-parameters/ | |
| let YOUR_DOMAIN = "YOUR_DOMAIN.TLD" // ex: scrapingbee.com | |
| function getParameterByName(name) { | |
| name = name.replace(/[\[]/, "\\[").replace(/[\]]/, "\\]"); | |
| var regex = new RegExp("[\\?&]" + name + "=([^&#]*)"), | |
| results = regex.exec(location.search); | |
| return results === null ? "" : decodeURIComponent(results[1].replace(/\+/g, " ")); | |
| } |
| CREATE TEMP FUNCTION BytesToUUID(data BYTES) | |
| RETURNS STRING | |
| LANGUAGE js AS """ | |
| const tableStr = "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/"; | |
| const atob = function (base64) { | |
| if (/(=[^=]+|={3,})$/.test(base64)) throw new Error("String contains an invalid character"); | |
| base64 = base64.replace(/=/g, ""); | |
| var n = base64.length & 3; | |
| if (n === 1) throw new Error("String contains an invalid character"); | |
| for (var i = 0, j = 0, len = base64.length / 4, bin = []; i < len; ++i) { |
| /** | |
| * Steps to use: | |
| * 1. Create CF Worker, copy and paste this in | |
| * 2. (Optional) Update configuration defaults | |
| * - If you want to manage in code, do so below under "Static Configuration" | |
| * - If you want dynamic custom config: Create CFW KV namespace, link them, and add reference below | |
| * | |
| * - You can overwrite default path prefix for loading analytics.js (<yourdomain>/ajs) | |
| * (corresponding KV entry: `script_path_prefix`) | |
| * - You can overwrite default path prefix for handling first-party data collection (<yourdomain>/data) |
Basecamp's new book Shape Up is now available online (https://basecamp.com/shapeup) to read page-by-page.
There is a .pdf version, but that's not the best format for Kindle / other eReaders. Instead, we can convert the page-by-page into an eReader friendly format.
NOTE: This has only been tested on Chrome
| animated.DialogOverlay = animated(DialogOverlay) | |
| animated.DialogContent = animated(DialogContent) | |
| function NewPostDialog({ date, show, onDismiss }) { | |
| const rootRef = useRef(null) | |
| const transitions = useTransition(show, null, { | |
| from: { opacity: 0, y: -10, blur: 0 }, | |
| enter: { opacity: 1, y: 0, blur: 8 }, | |
| leave: { opacity: 0, y: -10, blur: 0 }, |
| workflow "Deploy master" { | |
| on = "push" | |
| resolves = [ | |
| "alias", | |
| ] | |
| } | |
| action "install" { | |
| uses = "actions/npm@94e6933" | |
| args = "install" |
React recently introduced an experimental profiler API. This page gives instructions on how to use this API in a production release of your app.
Table of Contents
React DOM automatically supports profiling in development mode for v16.5+, but since profiling adds some small additional overhead it is opt-in for production mode. This gist explains how to opt-in.
React recently introduced an experimental profiler API. After discussing this API with several teams at Facebook, one common piece of feedback was that the performance information would be more useful if it could be associated with the events that caused the application to render (e.g. button click, XHR response). Tracing these events (or "interactions") would enable more powerful tooling to be built around the timing information, capable of answering questions like "What caused this really slow commit?" or "How long does it typically take for this interaction to update the DOM?".
With version 16.4.3, React added experimental support for this tracing by way of a new NPM package, scheduler. However the public API for this package is not yet finalized and will likely change with upcoming minor releases, so it should be used with caution.
