Bodhi Price bodhiprice

https://twitter.com/snookca/status/1073299331262889984?s=21

‪“‬In what way is JS any more maintainable than CSS? How does writing CSS in JS make it any more maintainable?”

‪Happy to chat about this. There’s an obvious disclaimer that there’s a cost to css-in-js solutions, but that cost is paid specifically for the benefits it brings; as such it’s useful for some usecases, and not meant as a replacement for all workflows. ‬

‪(These conversations always get heated on twitter, so please believe that I’m here to converse, not to convince. In return, I promise to listen to you too and change my opinions; I’ve had mad respect for you for years and would consider your feedback a gift. Also, some of the stuff I’m writing might seem obvious to you; I’m not trying to tell you if all people of some of the details, but it might be useful to someone else who bumps into this who doesn’t have context)‬

So the big deal about css-in-js (cij) is selectors.

Serverless plugin author's cheat sheet

This cheat sheet provides a detailed overview of the exposed lifecycle events and available commands (and entrypoints) of the Serverless framework, that can be hooked by plugins (internal and external ones). The document is structured by the commands invoked by the user.

Lifecycle events are shown as the globally available outer events (all providers) and sub lifecycle events that are provider specific in the called order. Currently only the AWS provider is shown. If you have information about the other provider,

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.~~

Tired of entering passwords again and again ?

Run this command to remember your password:

git config --global credential.helper 'cache --timeout 28800'

Above command will tell git to cache your password for 8 hours.

	Parameters:
	CanaryName:
	Type: String
	Default: my-canary
	MaxLength: 21

	Resources:
	CloudWatchSyntheticsRole:
	Type: AWS::IAM::Role
	Properties:

	server {
	location ~* (serviceworker\.js)$ {
	add_header 'Cache-Control' 'no-store, no-cache, must-revalidate, proxy-revalidate, max-age=0';
	expires off;
	proxy_no_cache 1;
	}
	}

	'use strict';
	exports.handler = (event, context, callback) => {

	// Get request and request headers
	const request = event.Records[0].cf.request;
	const headers = request.headers;

	// Configure authentication
	const authUser = 'user';
	const authPass = 'pass';

	'padding-line-between-statements': [2,
	// Always require blank lines after directive (like 'use-strict'), except between directives
	{blankLine: 'always', prev: 'directive', next: '*'},
	{blankLine: 'any', prev: 'directive', next: 'directive'},
	// Always require blank lines after import, except between imports
	{blankLine: 'always', prev: 'import', next: '*'},
	{blankLine: 'any', prev: 'import', next: 'import'},
	// Always require blank lines before and after every sequence of variable declarations and export
	{blankLine: 'always', prev: '*', next: ['const', 'let', 'var', 'export']},
	{blankLine: 'always', prev: ['const', 'let', 'var', 'export'], next: '*'},

	const axios = require('axios');
	const http = require('http');
	const https = require('https');

	module.exports = axios.create({
	//60 sec timeout
	timeout: 60000,

	//keepAlive pools and reuses TCP connections, so it's faster
	httpAgent: new http.Agent({ keepAlive: true }),

	# Dont forget to set the env variable "certdomain", and either fill in your email below or use an env variable for that too.
	# Also note that this config is using the LetsEncrypt staging server, remove the flag when ready!

	Resources:
	sslSecurityGroupIngress:
	Type: AWS::EC2::SecurityGroupIngress
	Properties:
	GroupId: {"Fn::GetAtt" : ["AWSEBSecurityGroup", "GroupId"]}
	IpProtocol: tcp
	ToPort: 443