Manos Konstantinidis manosim

This was tested on a FRESH Raspbian Bookworm Lite installation. Proceed with caution.

EDIT 23/12/2023: Removed dead download link and added own release

EDIT 09/06/2024: Force wayland after install

EDIT 06/07/2024: Add Troubleshooting section

EDIT 11/09/2024: Rearrange config file

Update package.json, set version to a prerelease version, e.g. 2.0.0-rc1, 3.1.5-rc4, ...
Run npm pack to create package
Run npm publish <package>.tgz --tag next to publish the package under the next tag
Run npm install --save package@next to install prerelease package

This is a proposal for a lightning talk at the Reactive 2016 conference.

NOTE: If you like this, star ⭐ the Gist - the amount of stars decides whether it makes the cut! You could also Retweet if you want :)

Get Flow

Type checking JavaScript with Flow

JavaScript is a dynamic language, and there's nothing wrong with that. It allows quick iteration and lowers barriers. However, sometimes some compile-time type checking is just what you need to keep your code in line and give yourself the confidence to build bigger and faster. Flow gives the best of both worlds. You can have normal JavaScript but you can also add types where they're helpful, and it adds zero cost at runtime. In this talk I'll show Flow as it applies to a Redux & React codebase.

You are probably here because you got the following error messages:

addComponentAsRefTo(...): Only a ReactOwner can have refs. You might be adding a ref to a component that was not created inside a component's render method, or you have multiple copies of React loaded.

This usually means one of two things:

You are trying to add a ref to an element that is being created outside of a component's render() function.
You have multiple (conflicting) copies of React loaded (eg. due to a miss-configured NPM dependency)

Invalid Refs

	// This file allows us to inspect the traffic going over the Native <-> JS bridge, and can be
	// helpful for debugging. Setting this to true should never be committed to git
	const ENABLE_BRIDGE_DEBUGGER = false; // <-- THIS SHOULD NOT BE TRUE IN MASTER!!!!

	// if true, function arguments will get pretty printed
	const PRETTY_PRINT = false;

	// enable this if you want to ignore EVERY event, except for the ones that match the `FOCUSED_*`
	// constants. If true, you configure what you want to see. If false, you configure what you DONT
	// want to see.

	def _get_displayed_page_numbers(current, final):
	"""
	This utility function determines a list of page numbers to display, based
	on the same pagination display style that GitHub use in their issue list pages.

	This gives us a nice contextually relevant set of page numbers to display.

	For example:
	current=14, final=16 -> [1, 2, None, 12, 13, 14, 15, 16]
	current=2, final=16 -> [1, 2, 3, 4, 5, None, 15, 16]

	/**
	* Add attributes to each object of an array.
	*
	* @param {array} foo - Array of objects where we will add the attibutes
	* @param {function} iterator
	*/
	_.each(foo, function(element, index) {
	_.extend(element, {field1: index}, {field2: 'bar', field3: 'baz'});
	});

	#!/bin/bash
	#
	# This script configures WordPress file permissions based on recommendations
	# from http://codex.wordpress.org/Hardening_WordPress#File_permissions
	#
	# Author: Michael Conigliaro <mike [at] conigliaro [dot] org>
	#
	WP_OWNER=www-data # <-- wordpress owner
	WP_GROUP=www-data # <-- wordpress group
	WP_ROOT=$1 # <-- wordpress root directory

	<!doctype html>
	<title>Site Maintenance</title>
	<style>
	body { text-align: center; padding: 150px; }
	h1 { font-size: 50px; }
	body { font: 20px Helvetica, sans-serif; color: #333; }
	article { display: block; text-align: left; width: 650px; margin: 0 auto; }
	a { color: #dc8100; text-decoration: none; }
	a:hover { color: #333; text-decoration: none; }
	</style>

	#!/usr/bin/env bash
	curl https://s3.amazonaws.com/heroku-jvm-buildpack-vi/vim-7.3.tar.gz --output vim.tar.gz
	mkdir vim && tar xzvf vim.tar.gz -C vim
	export PATH=$PATH:/app/vim/bin