Nick Carbone codenickycode

https://beta.reactjs.org/learn/your-first-component#nesting-and-organizing-components

Components can render other components, but you must never nest their definitions:

export default function Gallery() {
  // 🔴 Never define a component inside another component!
  function Profile() {
    // ...
  }
 // ...

https://beta.reactjs.org/learn/editor-setup#:~:text=If%20your%20ESLint,your%20continuous%20integration.

If your ESLint preset has formatting rules, they may conflict with Prettier. We recommend to disable all formatting rules in your ESLint preset using eslint-config-prettier so that ESLint is only used for catching logical mistakes. If you want to enforce that files are formatted before a pull request is merged, use prettier --check for your continuous integration.

Adapted from RemcoProgrammer's answer here:

Use Case	Solution	Example
Backend Cache	React Query, Apollo Client	fetch response
Navigation State	React Router	URL, params, history state
Component State (and subtree)	useState, custom hooks	is this thing currently open, what are the form contents and errors, what page of the table are we looking at
Unchanging Global State	useContext	auth, theme, language choice
Changing Global State	Redux, Zustand	dashboard data

	import path from 'path';
	import { fileURLToPath } from 'url';

	const currentModuleURL = import.meta.url;

	const pathToFile = fileURLToPath(currentModuleURL);
	console.log(pathToFile);
	//=> /Users/nick/Repos/node-test/path.js

	console.log(path.dirname(pathToFile));

	# Argument outside the build stage
	# To be used in first FROM
	ARG <key>=<value>

	# Parent image
	FROM [--platform=<platform>] <image> [AS <name>]
	# or
	FROM [--platform=<platform>] <image>[:<tag>] [AS <name>]
	# or
	FROM [--platform=<platform>] <image>[@<digest>] [AS <name>]

	# List all running containers
	docker ps

	# List all running and stopped containers
	docker ps -a

	# List all local images
	docker images

	# List all volumes

	# MacOs
	ipconfig getifaddr en0

	# Windows
	ipconfig /all

	# Linux
	hostname -I

	https://www.youtube.com/watch?v=eWEgUcHPle0

	___

	https://dev.to/hemanth/explain-csrf-like-im-five

	CSRF (Cross Site Request Forgery) is also known as Sea-Surf or Session Riding. It's is a form of trick that bad folks play on the browser in order to get it to do unexpected things in applications that you're already logged in.

	For example, imagine you were logged into your Supercell game on the internet. You get an e-mail saying "Click here to get 500 gems for free!". Clicking on the text, on the contrary, will actually initiate a request to Supercell to transfer all your gems to the hacker's account. Now, along with the request, the browser always sends the cookies to Supercell as well. Supercell verifies if the cookies are valid (which they are because you just logged in!), Supercell will trust the browser and the request and doesn't know that this is not what you wanted. They will go ahead and execute this instruction thinking this is what you wanted to do.

	type City = CityName \| CityCoordinates;

	type CityName = 'New York' \| 'Mumbai' \| 'Lagos';

	type CityCoordinates = {
	x: number;
	y: number;
	};

	type User = {