Darius itsMapleLeaf

Multiple GitHub accounts (Work vs Personal)

This setup uses some tricks to ensure that the right email/name/ssh-key is used for the right repos without having to think about it ever again.

First generate two SSH keys, ~/.ssh/id_ed25519 and ~/.ssh/id_ed25519_work
Add one key to your personal account and the other to your work account

`.ssh/config`

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:

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.
If the package is used in an async context, you could use await import(…) from CommonJS instead of require(…).
Stay on the existing version of the package until you can move to ESM.

Replacing Create React App with the Next.js CLI

How dare you make a jab at Create React App!?

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.

So why

Stop using JWTs!

TLDR: JWTs should not be used for keeping your user logged in. They are not designed for this purpose, they are not secure, and there is a much better tool which is designed for it: regular cookie sessions.

If you've got a bit of time to watch a presentation on it, I highly recommend this talk: https://www.youtube.com/watch?v=pYeekwv3vC4 (Note that other topics are largely skimmed over, such as CSRF protection. You should learn about other topics from other sources. Also note that "valid" usecases for JWTs at the end of the video can also be easily handled by other, better, and more secure tools. Specifically, PASETO.)

A related topic: Don't use localStorage (or sessionStorage) for authentication credentials, including JWT tokens: https://www.rdegges.com/2018/please-stop-using-local-storage/

The reason to avoid JWTs comes down to a couple different points:

The JWT specification is specifically designed only for very short-live tokens (~5 minute or less). Sessions

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

Profiling in production
- Create React App
- Webpack 4

Profiling in production

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.

	A::B is a system with 4 tokens: `A#`, `#A`, `B#` and `#B`.

	An A::B program is a sequence of tokens. Example:

	B# A# #B #A B#

	To compute a program, we must rewrite neighbor tokens, using the rules:

	A# #A ... becomes ... nothing
	A# #B ... becomes ... #B A#

	import { useFetcher } from "@remix-run/react";
	import { useCallback, useMemo } from "react";

	export function useRevalidator() {
	let fetcher = useFetcher();

	let revalidate = useCallback(
	() => {
	fetcher.submit(null, { action: "/", method: "post" });
	},

	# Logs
	logs
	*.log
	npm-debug.log*
	yarn-debug.log*
	yarn-error.log*
	lerna-debug.log*

	# Diagnostic reports (https://nodejs.org/api/report.html)
	report.[0-9].[0-9].[0-9].[0-9].json

	More recent resolution:

	1. cd ~/../../etc (go to etc folder in WSL).
	2. echo "[network]" \| sudo tee wsl.conf (Create wsl.conf file and add the first line).
	3. echo "generateResolvConf = false" \| sudo tee -a wsl.conf (Append wsl.conf the next line).
	4. wsl --terminate Debian (Terminate WSL in Windows cmd, in case is Ubuntu not Debian).
	5. cd ~/../../etc (go to etc folder in WSL).
	6. sudo rm -Rf resolv.conf (Delete the resolv.conf file).
	7. In windows cmd, ps or terminal with the vpn connected do: Get-NetIPInterface or ipconfig /all for get the dns primary and
	secondary.

	export function composeGetter<K extends string>(prop: K) {
	function getter<T extends { [P in K]?: any }>(object: T): T[typeof prop]
	function getter<T extends { [P in K]: any }>(object: T) {
	return object[prop]
	}

	return getter
	}

	export function composeSetter<K extends string>(prop: K) {