addyosmani

Ember.js currently doesn't have baked in support for Service Worker. They want this and there's an ember-cli RFCS thread discussing strategies however a number of tooling efforts exist to help fill in this gap today.

Note: you can of course just write vanilla Service Worker code for your Ember.js apps and that will work just fine. This doc tracks tooling and libraries that lower the friction for getting this setup

Service Worker Libraries

• sw-precache
• sw-toolbox

These static resource precaching and runtime caching libraries are lower-level than Broccoli, but can be used directly

toranb

import Ember from 'ember';
import hbs from 'htmlbars-inline-precompile';

export default Ember.Component.extend({
  layout: hbs`
    {{yield}}
  `
});

simurai

For minimalist ❤️ ers

• Settings > Core Settings > Title Bar: hidden
• Settings > Packages > Tabs > Always Show Tab Bar: false
• Settings > Themes > UI Theme: Apex https://atom.io/themes/apex-ui
• Settings > Themes > Syntax Theme: Apex https://atom.io/themes/apex-syntax

Just you, your code and nothing else.... :meditatingbuddha:

aranajhonny

FROM ruby:2.3.3
RUN apt-get update -qq && apt-get install -y build-essential libpq-dev nodejs
RUN mkdir /app
WORKDIR /app
ADD Gemfile /app/Gemfile
ADD Gemfile.lock /app/Gemfile.lock
RUN bundle install
ADD . /app
EXPOSE 3000
CMD rails s -p 3000

Rich-Harris

A hastily-written strawman for how bare imports could be resolved in browsers — see this convo.

mupkoo

image: node:7.10

cache:
  paths:
    - node_modules/
    - bower_components/

before_script:
  # Install Chrome
  - wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add -

Heydon

// Elements with `data-observe` toggle `data-visible`
// between `true` and `false`

if ('IntersectionObserver' in window) {
  const callback = (entries, observer) => {
    entries.forEach(entry => {
      entry.target.setAttribute('data-visible', entry.isIntersecting)
    })
  }
  

ceejbot

ESM modules in node: npm edition

The proposal you’re about to read is not just a proposal. We have a working implementation of almost everything we discussed here. We encourage you to checkout and build our branch: our fork, with the relevant branch selected. Building and using the implementation will give you a better understanding of what using it as a developer is like.

Our implementation ended up differing from the proposal on some minor points. As our last action item before making a PR, we’re writing documentation on what we did. While I loathe pointing to tests in lieu of documentation, they will be helpful until we complete writing docs: the unit tests.

This repo also contains a bundled version of npm that has a new command, asset. You can read the documentation for and goals of that comma

rsms

Font "package manager"

I've been thinking about creating a font management service similar to traditional software package managers (e.g. Debian Aptitude, NPM, etc.)

The basic idea is this:

1. There's a main repository of fonts that are free (as in free to distribute) that the working group hosts
2. There's a small program that serves as the "manager", to be used or installed on client systems
3. The "manager" can be configured to operate with multiple repositories

ryanflorence

import React, { Suspense, useState } from "react";
import { unstable_createResource as createResource } from "react-cache";
import {
  Autocomplete as Combobox,
  Input as ComboboxInput,
  List as ComboboxList,
  Option as ComboboxOption
} from "./Combobox";

function App({ tabIndex, navigate }) {