Sébastien Vanvelthem belgattitude

Why

Although @setup/node as a built-in cache option, it lacks an opportunity regarding cache persistence. Depending on usage, the action below might give you faster installs and potentially reduce carbon emissions (♻️🌳❤️).

Requirements

pnpm v7 or v8 (not using pnpm ? see the corresponding yarn action gist)

Bench

Why

Although @setup/node as a built-in cache option, it lacks an opportunity regarding cache persistence. Depending on usage, the action below might give you faster installs and potentially reduce carbon emissions (♻️🌳❤️).

Requirements

Yarn 3+/4+ with nodeLinker: node-modules. (Not using yarn ? see the corresponding pnpm 7/8+ action gist)

Structure

keyword: material ui, mui, typescript, intellisense, vscode

microsoft/TypeScript#39326

microsoft/TypeScript#34801

When using mui with typescript, there is performance issue with vscode intellisense, because of type checking.

I've read the comments and found a clue that some csstypes given by mui might be source of issue.

`Option` vs non-`Option`

	`Option<T>`	non-`Option` (`T \| undefined`)
accessing property	`userOption.map(user => user.age)`	`userNullish?.age`
calling a method	`userOption.map(user => user.fn())`	`userNullish?.fn()`
providing fallback	`ageOption.getOrElse(0)`	`ageNullish ?? 0`
filter	`ageOption.filter(checkIsOddNumber)`	`ageNull

58 bytes of CSS to look great nearly everywhere

When making this website, i wanted a simple, reasonable way to make it look good on most displays. Not counting any minimization techniques, the following 58 bytes worked well for me:

main {
  max-width: 38rem;
  padding: 2rem;
  margin: auto;
}

	#!/bin/bash

	# Function to display usage information
	usage() {
	echo "Usage: $0 /path/to/input.mp4 [ /path/to/output_directory ]"
	exit 1
	}

	# Check if at least one argument (input file) is provided
	if [ $# -lt 1 ]; then

	// Using:
	// [email protected]
	// [email protected]

	import globby from 'globby';
	import { dirname } from 'path';
	import { fileURLToPath } from 'url';
	import chalk from 'chalk';

	async function main() {

	import { useCallback, useLayoutEffect, DependencyList } from 'react'

	/**
	* This version bounces each version of the callback. This ensures that the callback
	* will be called with each state of the application. That's why `deps` is a required argument.
	*
	* Previous version used `useRef` for `timeoutId` and didn't have `deps` argument.
	* This resulted in missing calling the callback for the previous state and necessarily
	* calling it for the new state.
	*

	<?php

	namespace AppBundle\Form;


	use Symfony\Component\Form\AbstractType;
	use Symfony\Component\Form\Extension\Core\Type\PasswordType;
	use Symfony\Component\Form\Extension\Core\Type\RepeatedType;
	use Symfony\Component\Form\Extension\Core\Type\SubmitType;
	use Symfony\Component\Form\FormBuilderInterface;

	<!doctype html>
	<html><head><script src="app.js"></script></head><body></body></html>

Sébastien Vanvelthem belgattitude

Why

Requirements

Bench

Why

Requirements

Structure

Option vs non-Option

58 bytes of CSS to look great nearly everywhere

`Option` vs non-`Option`