| // Feedback requested on the useDeepCompareEffect | |
| // it just feels like a bit of work... | |
| // HERE'S THE REASON I NEED THIS: | |
| // when people use the useQuery hook, they'll typically | |
| // do so like this: `useQuery(myQuery, {var1: props.value})` | |
| // which means that passing `variables` to `useEffect` will | |
| // trigger a rerun of the callback even if they didn't | |
| // actually change (referrential equality) | |
| function useQuery({query, variables}) { |
| import λ from "apex.js"; | |
| import { Pool } from "pg"; | |
| // connection details inherited from environment | |
| const pool = new Pool({ | |
| max: 1, | |
| min: 0, | |
| idleTimeoutMillis: 120000, | |
| connectionTimeoutMillis: 10000 | |
| }); |
| { | |
| "parser": "@typescript-eslint/parser", | |
| "parserOptions": { | |
| "project": "./tsconfig.json", | |
| "tsconfigRootDir": "." | |
| }, | |
| "env": { | |
| "browser": true, | |
| "jest/globals": true | |
| }, |
Copyright © <year> <copyright holders>
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
| /** | |
| * Basic example of routerless store based routing. | |
| * To understand what is going on check out | |
| * https://svelte.dev/tutorial/writable-stores | |
| * https://www.npmjs.com/package/feather-route-matcher | |
| */ | |
| // stores.js |
| <!DOCTYPE html> | |
| <meta charset="utf-8"> | |
| <title>Twitter Archive Viewer</title> | |
| <script>window.YTD = { tweet: {} }</script> | |
| <script src="tweet.js"></script><!-- this is loading a file from the archive --> | |
| <style> | |
| .tweet { border: 1px solid #eee; margin: 8px } | |
| .full_text { padding: 8px } | |
| .created_at { padding: 8px; color: #777 } | |
| </style> |
| On void linux. | |
| Under `/etc/containers/` there is a file called `registries.conf`. It is complemented by `man 5 containers-registries.conf`. | |
| Change (for me lines 11-12) which say | |
| [registries.search] | |
| registries = [] | |
| { | |
| "lv_module": { | |
| "scope": "elixir, html-eex", | |
| "prefix": "lv", | |
| "body": [ | |
| "defmodule ${1}Web.${2}Live do", | |
| " use ${1}Web, :live_view", | |
| "end" | |
| ], | |
| "description": "LiveView module" |
Firstly, Create React App is good. But it's a very rigid CLI, primarily designed for projects that require very little to no configuration. This makes it great for beginners and simple projects but unfortunately, this means that it's pretty non-extensible. Despite the involvement from big names and a ton of great devs, it has left me wanting a much better developer experience with a lot more polish when it comes to hot reloading, babel configuration, webpack configuration, etc. It's definitely simple and good, but not amazing.
Now, compare that experience to Next.js which for starters has a much larger team behind it provided by a world-class company (Vercel) who are all financially dedicated to making it the best DX you could imagine to build any React application. Next.js is the 💣-diggity. It has amazing docs, great support, can grow with your requirements into SSR or static site generation, etc.
| import type { Action, Loader } from "@remix-run/loader"; | |
| import { json, parseFormBody, redirect } from "@remix-run/loader"; | |
| import { readTodos, createTodo, deleteTodo } from "../data/todo"; | |
| let action: Action = async ({ request, context: { session } }) => { | |
| let [method, body] = await methodOverride(request); | |
| await new Promise((res) => setTimeout(res, 1000)); | |
| switch (method) { | |
| case "post": { | |
| let [_, error] = await createTodo(body!.name); |
