Maël Mayon Baldrani

Replacing Create React App with the Next.js CLI

How dare you make a jab at Create React App!?

Firstly, Create React App is good. But it's a very rigid CLI, primarily designed for projects that require very little to no configuration. This makes it great for beginners and simple projects but unfortunately, this means that it's pretty non-extensible. Despite the involvement from big names and a ton of great devs, it has left me wanting a much better developer experience with a lot more polish when it comes to hot reloading, babel configuration, webpack configuration, etc. It's definitely simple and good, but not amazing.

Now, compare that experience to Next.js which for starters has a much larger team behind it provided by a world-class company (Vercel) who are all financially dedicated to making it the best DX you could imagine to build any React application. Next.js is the 💣-diggity. It has amazing docs, great support, can grow with your requirements into SSR or static site generation, etc.

So why

Vue.js and Vuex - best practices for managing your state

Modifying state object

Example

If you have to extend an existing object with additional property, always prefer Vue.set() over Object.assign() (or spread operator).

Example below explains implications for different implementations.

How to setup Gandi.net domain routing to Heroku

TODO: setup SSL.

This is a quick guide on how to setup domain and infinite subdomains, in a case where, for example, you may have one subdomain for each client.

Starting from this http://stackoverflow.com/a/39646701

Source: https://apple.stackexchange.com/questions/138941/how-do-i-stop-the-adobe-creative-cloud-app-from-auto-launching-on-login

It is loaded by default by /Library/LaunchAgents/com.adobe.AdobeCreativeCloud.plist.

If you run

launchctl unload -w /Library/LaunchAgents/com.adobe.AdobeCreativeCloud.plist

	# Reference: https://www.exclamationlabs.com/blog/continuous-deployment-to-npm-using-gitlab-ci/

	# GitLab uses docker in the background, so we need to specify the
	# image versions. This is useful because we're freely to use
	# multiple node versions to work with it. They come from the docker
	# repo.
	# Uses NodeJS V 9.4.0
	image: node:9.4.0

	# And to cache them as well.

	"prettier": {
	"useTabs": true,
	"semi": false,
	"singleQuote": false,
	"bracketSpacing": true,
	"trailingComma": "es5",
	"printWidth": 160
	},
	"eslintConfig": {
	"parserOptions": {

	#!/bin/bash

	echo ""

	echo "`date`: RUNNING: brew update"
	/usr/local/bin/brew update
	echo "`date`: FINISHED: brew update"

	echo ""

	/*--- waitForKeyElements(): A utility function, for Greasemonkey scripts,
	that detects and handles AJAXed content.

	Usage example:

	waitForKeyElements (
	"div.comments"
	, commentCallbackFunction
	);