Gregor MacLennan gmaclennan

Pure ESM package

The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.

This means you have the following choices:

Use ESM yourself. (preferred)
Use import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.
If the package is used in an async context, you could use await import(…) from CommonJS instead of require(…).
Stay on the existing version of the package until you can move to ESM.

In addition to the Storybook for React setup, you'll also need to install these packages:

npm i -D @babel/core babel-loader css-loader style-loader

I've designed a lot of RPC protocols in my career. One pattern that's worked well basically goes as follows:

// Client calls: print('Hello World\n')
-> [1, "print", "Hello World!\n"]
// Server sends return value (or lack of return vvalue)
<- [-1]

// Client calls: add(1, 2)
-> [2, "add", 1, 2]

First, let's note the difference in philosophy: TypeScript aims for fast analysis because you can to compile it down to JS before you can run/test it. flowtype is meant to be an async analysis that can run continuously with changes since the last analysis, or in parallel with your eslint and bundler rules. As such, flowtype's type system and analysis is not quite as concerned with speed or memory usage in service of potentially finding more bugs.

On two occasions I have tried to roll out flow in React Native applications, and on those two occasions we ended up backing out after a few weeks. Some detail: flow doesn't have a public roadmap, and what version you use is dictated by the react/react-native dependency and the annotations in react-native itself. flowtype also has some hard-coded aspects to help the analysis for React, so major updates to React itself sometimes also require updating flowtype to match. React Native upgrades then get gated based on your dependent libraries (or flow-typed) being updated

Folder Structure

Please note

While this gist has been shared and followed for years, I regret not giving more background. It was originally a gist for the engineering org I was in, not a "general suggestion" for any React app.

Typically I avoid folders altogether. Heck, I even avoid new files. If I can build an app with one 2000 line file I will. New files and folders are a pain.

	#!/bin/bash

	CLEAR='\033[0m'
	RED='\033[0;31m'

	function usage() {
	if [ -n "$1" ]; then
	echo -e "${RED}👉 $1${CLEAR}\n";
	fi
	echo "Usage: $0 [-n number-of-people] [-s section-id] [-c cache-file]"

	package com.example.sample.offline

	import android.util.Log
	import java.io.BufferedReader
	import java.io.ByteArrayOutputStream
	import java.io.FileNotFoundException
	import java.io.PrintStream
	import java.net.ServerSocket
	import java.net.Socket
	import kotlin.math.pow

	(function(window, undefined) {
	var SITE_ID = null;
	var NETLIFY_API = "https://api.netlify.com";
	var NetlifyError = function(err) {
	this.err = err;
	};
	NetlifyError.prototype.toString = function() {
	return this.err.message;
	};
	var authWindow, base, providers;

	console.log('Loading event');

	var Q = require('q');
	var aws = require('aws-sdk');
	var cloudfront = new aws.CloudFront();

	exports.handler = function (event, context) {
	//_log('Received event: ', event);

	var bucket = event.Records[0].s3.bucket.name;

	# Criando um script .sh para executar todos os comandos:
	#root@servidor:~# vi script.sh
	#root@servidor:~# chmod +x script.sh
	#root@servidor:~# ./script.sh

	apt-get update
	apt-get -y install autoconf automake build-essential git-core libass-dev libgpac-dev libsdl1.2-dev libtheora-dev libtool libvdpau-dev libvorbis-dev libx11-dev libxext-dev libxfixes-dev pkg-config texi2html zlib1g-dev libmp3lame-dev nasm gcc yasm && true
	mkdir ~/ffmpeg_sources
	cd ~/ffmpeg_sources
	git clone --depth 1 git://github.com/mstorsjo/fdk-aac.git