Joscha Feth joscha

An exploration of the different render methods available in react-enzyme.

Why

Doing require extensions correctly is essential, because:

Users should be able to install multiple extensions in succession, and have them work together.
Coverage tools like nyc need it to reliably supply coverage information that takes into account sourcemaps from upstream transforms.
Because non-standard, un-predictable behavior causes hard to solve bugs, and major headaches for project maintainers.

What is a require extension anyways?

From Meteor's documentation:

In Meteor, your server code runs in a single thread per request, not in the asynchronous callback style typical of Node. We find the linear execution model a better fit for the typical server code in a Meteor application.

This guide serves as a mini-tour of tools, trix and patterns that can be used to run async code in Meteor.

Basic async

Sometimes we need to run async code in Meteor.methods. For this we create a Future to block until the async code has finished. This pattern can be seen all over Meteor's own codebase:

Introduction

An introduction to curl using GitHub's API.

The Basics

Makes a basic GET request to the specifed URI

curl https://api.github.com/users/caspyin

	###
	### [2023-06-19] UPDATE: Just tried to use my instructions again on a fresh install and it failed in a number of places.
	###. Not sure if I'll update this gist (though I realise it seems to still have some traffic), but here's a list of
	###. things to watch out for:
	### - Check out the `nix-darwin` instructions, as they have changed.
	### - There's a home manager gotcha https://github.com/nix-community/home-manager/issues/4026
	###

	# I found some good resources but they seem to do a bit too much (maybe from a time when there were more bugs).
	# So here's a minimal Gist which worked for me as an install on a new M1 Pro.

	with import <nixpkgs> {
	overlays = map (uri: import (fetchTarball uri)) [
	https://github.com/mozilla/nixpkgs-mozilla/archive/master.tar.gz
	];
	};

	stdenv.mkDerivation {
	name = "rust-wasm";
	buildInputs = [
	cargo-web

	Copyright [2012] [Gianluca Tessarolo]

	Licensed under the Apache License, Version 2.0 (the "License");
	you may not use this file except in compliance with the License.
	You may obtain a copy of the License at

	http://www.apache.org/licenses/LICENSE-2.0

	Unless required by applicable law or agreed to in writing, software
	distributed under the License is distributed on an "AS IS" BASIS,

	#!/bin/sh

	# Pre-commit hook passing files through jshint

	ROOT_DIR=$(git rev-parse --show-toplevel) # gets the path of this repo
	CONF="--config=${ROOT_DIR}/build/config/jshint.json" # path of your jshint config
	JSHINT=$(which jshint) # jshint path

	if git rev-parse --verify HEAD >/dev/null 2>&1
	then

	<ivysettings>
	<!-- Build.scalaのsettingsにexternalIvySettings()を追加すると有効 -->
	<caches useOrigin="true"/>
	<settings defaultResolver="play"/>
	<resolvers>
	<chain name="play">
	<filesystem name="1">
	<!-- ここは絶対パスじゃないとだめ。playの${sbt.ivy.home}は相対パスだった -->
	<artifact pattern="/Users/yasushi/src/play/play-2.0/repository/local/[organisation]/[module]/[revision]/[type]s/[artifact].[ext]" />
	</filesystem>