Ganapati V S ganapativs

Time Travel Debugging

Time Travel refers to the ability to record a tab and later replay it ([WebReplay][wrr]). The technology is useful for local development, where you might want to:

pause and step forwards or backwards
pause and rewind to a prior state
rewind to the time a console message was logged
rewind to the time an element had a certain style or layout
rewind to the time a network asset loaded

How we incorporate next and cloudfront (2018-04-21)

Feel free to contact me at [email protected] or tweet at me @statisticsftw

This is a rough outline of how we utilize next.js and S3/Cloudfront. Hope it helps!

It assumes some knowledge of AWS.

Goals

FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.

Effective Engineer - Notes

By Edmond Lau
Highly Recommended 👍
http://www.theeffectiveengineer.com/

What's an Effective Engineer?

Stuff I wish I'd known sooner about service workers

I recently had several days of extremely frustrating experiences with service workers. Here are a few things I've since learned which would have made my life much easier but which isn't particularly obvious from most of the blog posts and videos I've seen.

I'll add to this list over time – suggested additions welcome in the comments or via twitter.com/rich_harris.

Use Canary for development instead of Chrome stable

~~Chrome 51 has some pretty wild behaviour related to console.log in service workers. Canary doesn't, and it has a load of really good service worker related stuff in devtools.~~

	{
	"name": "tsquickstart",
	"version": "1.0.0",
	"description": "Boilerplate for quick one-off TypeScript projects. Just run `npm start`",
	"scripts": {
	"init": "test -f tsconfig.json \|\| (tsc --init -t ESNext -m ESNext && npm install)",
	"start": "npm run init && concurrently \"npm run watch\" \"npm run serve\"",
	"serve": "http-server",
	"watch": "tsc -p . --watch",
	"build": "tsc -p ."

	# Generate a new pgp key: (better to use gpg2 instead of gpg in all below commands)
	gpg --gen-key
	# maybe you need some random work in your OS to generate a key. so run this command: `find ./* /home/username -type d \| xargs grep some_random_string > /dev/null`

	# check current keys:
	gpg --list-secret-keys --keyid-format LONG

	# See your gpg public key:
	gpg --armor --export YOUR_KEY_ID
	# YOUR_KEY_ID is the hash in front of `sec` in previous command. (for example sec 4096R/234FAA343232333 => key id is: 234FAA343232333)

	const file = this.input.files[0];
	//console.log(file);
	var xhr = new XMLHttpRequest();
	xhr.addEventListener('load', (e) => {
	console.log(e.target.response);
	});
	xhr.open('POST', host + 'fileuploadstream', true);
	xhr.setRequestHeader('body', JSON.stringify({ id: 'somebucketfolderid', fn: file.name }));
	xhr.send(file);

	#!/bin/bash

	for file in $(git diff --cached --name-only \| grep -E '\.(js\|jsx)$')
	do
	git show ":$file" \| node_modules/.bin/eslint --stdin --stdin-filename "$file" # we only want to lint the staged changes, not any un-staged changes
	if [ $? -ne 0 ]; then
	echo "ESLint failed on staged file '$file'. Please check your code and try again. You can run ESLint manually via npm run eslint."
	exit 1 # exit with failure status
	fi
	done