Patrick Lienau rozzzly

Disable Device Enrollment Program (DEP) notification on macOS Ventura.md

Ventura docs for M2 Macs in this comment: https://gist.github.com/henrik242/65d26a7deca30bdb9828e183809690bd?permalink_comment_id=4555340#gistcomment-4555340

Old Monterey docs in this old revision: https://gist.github.com/henrik242/65d26a7deca30bdb9828e183809690bd/32c410e3a1de73539c76fa13ea5486569c4e0c5d

Solution for Sonoma: https://gist.github.com/sghiassy/a3927405cf4ffe81242f4ecb01c382ac

Note:

When this guide is more complete, the plan is to move it into Prepack documentation.
For now I put it out as a gist to gather initial feedback.

A Gentle Introduction to Prepack (Part 1)

If you're building JavaScript apps, you might already be familiar with some tools that compile JavaScript code to equivalent JavaScript code:

Babel lets you use newer JavaScript language features, and outputs equivalent code that targets older JavaScript engines.

ESM modules in node: npm edition

The proposal you’re about to read is not just a proposal. We have a working implementation of almost everything we discussed here. We encourage you to checkout and build our branch: our fork, with the relevant branch selected. Building and using the implementation will give you a better understanding of what using it as a developer is like.

Our implementation ended up differing from the proposal on some minor points. As our last action item before making a PR, we’re writing documentation on what we did. While I loathe pointing to tests in lieu of documentation, they will be helpful until we complete writing docs: the unit tests.

This repo also contains a bundled version of npm that has a new command, asset. You can read the documentation for and goals of that comma

Render 1	Render 2	State Preserved?
`<>...</>`	`<>{[...]}</>`	yes (in any level)
`<><>...</></>`	`<>...</>`	no
`[...]`	`[[...]]`	no
`[<>...</>]`*	`[...]`	no
`[<>...</>]`*	`<>...</>`	no
`[<>...</>]`*	`<>[...]</>`	no
`[<>...</>]`*	`[[...]]`	yes
`[<>...>]`*	`<><>...>>`	yes

	// Will only render the `content` or `render` elements if the tippy is mounted to the DOM.
	// Replace <Tippy /> with <LazyTippy /> component and it should work the same.

	const LazyTippy = forwardRef((props, ref) => {
	const [mounted, setMounted] = useState(false);

	const lazyPlugin = {
	fn: () => ({
	onMount: () => setMounted(true),
	onHidden: () => setMounted(false),

	#!/bin/bash

	CYAN="$(tput bold; tput setaf 6)"
	RESET="$(tput sgr0)"

	clear

	if command -v python3 > /dev/null 2>&1; then
	if [ $(python3 -c "print('ye')") = "ye" ]; then
	clear

	/*
	* The redux-orm model and redux-toolkit slice are defined together in the same
	* class.
	* An export scheme similiar to Ducks is used, where the model class is
	* exported in place of the reducer function.
	*/

	import { Model, fk, many, attr } from 'redux-orm';
	import { createSlice } from '@reduxjs/toolkit';

	Const WindowsFolder = 0
	Const SystemFolder = 1
	Const TempFolder = 2

	Dim objShell, regPath
	Set objShell = WScript.CreateObject("WScript.Shell")

	regPath = Array("HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows Kits\Installed Roots\WindowsDebuggersRoot10",_
	"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Kits\Installed Roots\WindowsDebuggersRoot10",_
	"HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows Kits\Installed Roots\WindowsDebuggersRoot81",_

	/**
	* This script was taken from a discussion on Google Groups.
	* I'm not taking credit for it but sharing it because it is very useful for splitting
	* discontinuous absolute paths into continuous subpaths. Where this is particularly
	* useful is for importing SVG files into applications like Figma, Sketch, InVision, XD, etc.
	*/
	/**
	* Split discontinuous absolute paths into continuous sub-paths.
	*
	* Example:

	Create a file:
	$ pico /Users/Shared/logoutHook.sh

	File content:
	#!/bin/bash
	say 'Hasta la vista baby!'

	Set exuction permission:
	$ sudo chmod +x /Users/Shared/logoutHook.sh