Quentin Renard ifox

Brew Bundle Brewfile Tips

Copyright & License

Unless otherwise noted (either in this file or in a file's copyright section) the contents of this gist are Copyright ©️2020 by Christopher Allen, and are shared under spdx:Creative Commons Attribution Share Alike 4.0 International (CC-BY-SA-4.) open-source license.

Sponsor

If you more tips and advice like these, you can become a monthly patron on my GitHub Sponsor Page for as little as $5 a month; and your contributions will be multipled, as GitHub is matching the first $5,000! This gist is all about Homebrew, so if you like it you can support it by donating to them or becoming one of their Github Sponsors.

Nginx + Let's Encrypt on Laravel Forge

Redirects everything to a new domain, but allows Let's Encrypt to issue and renew certificates.

Using the inbuilt redirect in Laravel Forge appears to prevent Let's Encrypt from verifying the domain.

Example - redirect everything to example.org - edit Nginx config as below:

location / {

Add the other user as a remote

#Using https
git remote add otheruser https://github.com/otheruser/yourrepo.git
# Or - Using SSH
git remote add otheruser [email protected]:otheruser/yourrepo.git

Fetch

git fetch otheruser

Why imperative imports are slower than declarative imports

A lot of people misunderstood Top-level await is a footgun, including me. I thought the primary danger was that people would be able to put things like AJAX requests in their top-level await expressions, and that this was terrible because await strongly encourages sequential operations even though a lot of the asynchronous activity we're talking about should actually happen concurrently.

But that's not the worst of it. Imperative module loading is intrinsically bad for app startup performance, in ways that are quite subtle.

Consider an app like this:

// main.js

Dynamic module loading done right

Follow-up to Top-level await is a footgun – maybe read that first

Here are some things I believe to be true:

Static module syntax is beneficial in lots of ways – code is easier to write (you get better linting etc) and easier to optimise (tree-shaking and other things that are only really possible with static syntax), and most importantly, faster to load (it's trivial for a module loader to load multiple dependencies concurrently when they're declared with a static syntax – not so with imperative statements like require(...) or await import(...)).
App startup time is perhaps when performance is most critical. (You already know this, I don't need to cite the studies.)
If you're in favour of constructs that jeopardise app startup time, you are anti-user. Top-level await is such a construct.

Stuff I wish I'd known sooner about service workers

I recently had several days of extremely frustrating experiences with service workers. Here are a few things I've since learned which would have made my life much easier but which isn't particularly obvious from most of the blog posts and videos I've seen.

I'll add to this list over time – suggested additions welcome in the comments or via twitter.com/rich_harris.

Use Canary for development instead of Chrome stable

~~Chrome 51 has some pretty wild behaviour related to console.log in service workers. Canary doesn't, and it has a load of really good service worker related stuff in devtools.~~

	#!/bin/bash

	# Colors
	RED='\033[0;31m'
	GREEN='\033[0;32m'
	NO_COLOR='\033[0m'
	BLUE='\033[0;34m'
	YELLOW='\033[0;33m'
	NO_COLOR='\033[0m'

	#!/usr/bin/env bash
	NC='\033[0m' # No Color
	YELLOW='\033[0;33m'
	CYAN='\033[0;36m'
	GREEN='\033[0;32m'
	RED='\033[0;31m'
	MAGENTA='\033[0;35m'

	notify_about_actions_required() {
	changed_files="$(git diff-tree -r --name-status --no-commit-id $1 $2)"

	<?php

	namespace App\Http\Middleware;

	use Closure;

	class RewriteLinks
	{
	/**
	* Handle an incoming request.

	trait HasEnums
	{
	/**
	* The array of enumerators of a given group.
	*
	* @param null\|string $group
	* @return array
	*/
	static function enums($group = null)
	{