crazy4groovy

import { UserProvider } from "./context"
import { Component } from "./component"

export default function App() {
  return (
    <UserProvider>
      <h1>Context App</h1>
      <Component />
      <br />
      <Component />

crazy4groovy

# https://docs.brev.dev/howto/automatically-set-up/

##### Homebrew #####
(echo ""; echo "##### Homebrew #####"; echo "";)
curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh | bash -
echo 'eval "$(/home/linuxbrew/.linuxbrew/bin/brew shellenv)"' >> /home/brev/.bash_profile
echo 'eval "$(/home/linuxbrew/.linuxbrew/bin/brew shellenv)"' >> /home/brev/.zshrc
eval "$(/home/linuxbrew/.linuxbrew/bin/brew shellenv)"

brew install fnm

crazy4groovy

type AnyFunction = (...args: any[]) => any

function useEvent<T extends AnyFunction>(callback?: T) {
  const ref = useRef<AnyFunction | undefined>(() => {
    throw new Error("Cannot call an event handler while rendering.")
  })
  useLayoutEffect(() => {
    ref.current = callback
  })
  return useCallback<AnyFunction>(

crazy4groovy

// credit: https://www.30secondsofcode.org/articles/s/javascript-object-array-proxy

const toKeyedArray = obj => {
  const methods = {
    map(target) {
      return (callback) =>
        Object.keys(target).map(key => callback(target[key], key, target));
    },
    reduce(target) {
      return (callback, accumulator) =>

crazy4groovy

// credit: https://www.30secondsofcode.org/articles/s/js-immutable-object-proxy

const term = {
  id: 1,
  value: 'hello',
  properties: [{ type: 'usage', value: 'greeting' }],
};

const immutable = obj =>
  new Proxy(obj, {

crazy4groovy

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

crazy4groovy

// No matter how impressive your design system is, there will always be times that small layout adjustments are required. This handy component lets you shift things around in small increments.

// credit: https://www.joshwcomeau.com/snippets/react-components/shift-by/

import React from 'react';
function ShiftBy({ x = 0, y = 0, children }) {
  return (
    <div
      style={{
        transform: `translate(${x}px, ${y}px)`,

crazy4groovy

{
  "applicationId": "js.neutralino.fpp",
  "port": 0,
  "version": "1.0.0",
  "defaultMode": "window",
  "documentRoot": "/",
  "url": "/react-app/build/",
  "enableServer": true,
  "enableNativeAPI": true,
  "tokenSecurity": "one-time",

crazy4groovy

$WC = New-Object net.webclient
$htmlUri = "https://www.google.com"
$jpgUri = "https://www.example.com/example-image.jpg"

$Content = $WC.DownloadString($htmlUri)

$WC.DownloadFile($jpgUri, "C:\Temp\myimage.jpg")

# see TLS 1.2: https://stackoverflow.com/questions/41618766/powershell-invoke-webrequest-fails-with-ssl-tls-secure-channel/41618979#41618979
# invoke-webrequest $jpgUri -Outfile "C:\Temp\myimage.jpg" 

crazy4groovy

import { Worker } from 'worker_threads';

import MyClient from './my-client.js';

const proxyAPI = new Worker(__dirname + "/server-worker.js");

define('Module1', () => {
  let client;
  beforeEach(() => {
  	client = new MyClient("http://localhost:5544");