Fabrício Tavares fabriciotav

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

MySQL

Getting started

Query Param API Examples

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions

Update 6/14/13

see https://gist.github.com/machty/5723945 for the latest API (unlikely to change from now on)
latest Ember build: https://machty.s3.amazonaws.com/ember/ember-async-routing-10.js

Router Facelift Examples

Guide to latest API enhancements router.js PR Ember PR

___an infinite space

45 ways to visualize two numbers http://blog.visual.ly/45-ways-to-communicate-two-quantities/

___navigating the infinite space

knights movement:

This is a brain dump of my experience trying to get something going with Ember.js. My goal was to get to know the ins and outs of the framework by completing a pretty well defined task that I had lots of domain knowledge about. In this case reproducing a simple Yammer feed. As of this time, I have not been able to complete that task. So this is a subjective rundown of the things I think make it difficult to get a handle on Ember. NOTE: My comments are addressing the Ember team and giving suggestions on what they could do to improve the situation.

App setup

The new guides have pretty good explanation of the various parts of the framework; routers, models, templates, views. But it's not clear how they all get strapped together to make something that works. There are snippets of examples all over the place like:

App.Router.map(function() {
  match('/home').to('home');
});

	# The workflow template is designed for Ember apps.
	#
	# It assumes certain dependencies and scripts in package.json. If
	# they don't apply to your project, feel free to remove irrelevant
	# code in the workflow. These can be inferred from the job name.
	#
	# {
	# "scripts": {
	# "build": "ember build --environment=production",
	# "build:test": "ember build --environment=test",