Matt Mankins mankins

I hereby claim:

To claim this, I am signing this object:

What's the current best practice for executing a function included by adding a (potentially async, deferred) script tag on the page?

We used to have scripts load synchronously, so we could immediately start using the library the next line:

<head>
<script src="/my-library-2001.js"/>
<script>
 myLib.hello(); // works!
</script>

	#!/bin/bash

	# From a user's MFA code, generate accesskey, secret, session token
	#
	# ENV inputs:
	# AWS_CLI_INPUT = /path/to/token/config.json
	# AWS_PROFILE = The Aws profile to use for aws commands

	MFA_CODE=$1
	if [ -z $MFA_CODE ]; then

	#!/bin/bash

	# parentWeighting factor will multiple weights, we will get this from the first argument, defaulting to 1
	parentWeighting=${1:-1}

	# Get the list of authors and commit counts
	authors=$(git log --format='%ae' \| sort \| uniq -c \| sort -nr)

	# Get the total weight
	total=$(echo "$authors" \| awk '{ sum += $1 } END { print sum }')

	#!/bin/bash

	#set -x

	# If there's a proxy host set in the environment, pull it in
	[ -n $FTAWS_PROXY_HOST ] && PROXYHOST=$FTAWS_PROXY_HOST

	# Private is the 'usual' way, subject to override in a few places below. If any code below selects public, then we go with the public address.
	PROXYTOIPTYPE="-r"