Matt Rossman mattrossman

Recently when refactoring a Vue 1.0 application, I utilized ES6 arrow functions to clean up the code and make things a bit more consistent before updating to Vue 2.0. Along the way I made a few mistakes and wanted to share the lessons I learned as well as offer a few conventions that I will be using in my Vue applications moving forward.

The best way to explain this is with an example so lets start there. I'm going to throw a rather large block of code at you here, but stick with me and we will move through it a piece at a time.

<script>

// require vue-resource...

new Vue({

How to connect Raspberry Pi to UMass Eduroam

Open up a terminal and move into the directory holding the wpa_supplicant config file.

cd /etc/wpa_supplicant

You may want to backup your config file before you do anything just in case.

sudo cp wpa_supplicant.conf ~/Desktop/wpa_supplicant.conf

These are the build tools I prefer to use when starting a new JavaScript or TypeScript library. Most libraries I write run both in the browser and in node.js. Each project needs to be lightweight, and to minimize maintenance. And I need build chains for those libraries to pretty much "just work". That last part has become more important over time, as I've maintained more libraries and generally had less time to deal with dependencies and build system issues. For web applications, as opposed to libraries consumed in other projects, these choices may or may not make sense. These are opinionated choices, and will probably change over time.

Almost always:

microbundle: Zero-config Rollup bundler, with optional TypeScript support
tape: Test runner
tap-spec: Clean test output

Occasionally:

auth0-react static getAccessToken method

There are many use cases to use getAccessTokenSilently outside of a component (for example, in an Axios Interceptor or an Apollo Client).

It's tempting to ask for the option to pass an Auth0Client instance into the Auth0Provider so that its getTokenSilently method can used outside of the context of a component, eg.

const client = new Auth0Client();
export const getAccessToken = () => client.getTokenSilently();

My Minimal TypeScript Monorepo Setup for ESM Libraries

After a deep dive looking up best practices for TypeScript monorepos recently, I couldn't find anything that suited my needs:

Publish individual (typed) packages to NPM with minimal config.
Supports fast unit testing that spans the entire project (e.g., via Vitest)
Ability to have an interactive playground to experiment with the API in a real-time (e.g., via Vite)

Most solutions point to TypeScript project references,

	// It is important to declare your variables.

	(function() {
	var foo = 'Hello, world!';
	print(foo); //=> Hello, world!
	})();

	// Because if you don't, the become global variables.

	(function() {