gmarcos87

const genericFile = require('./locales/en.json')
const colors = require('colors')

// Load all translation in locales folder
let translations = {}
require('fs').readdirSync('./locales/').forEach((file) => {
	if (file.match(/\.json$/) !== null) {
		let name = file.replace('.json', '')
		translations[name] = require('./locales/' + file)

serapath

use require in a codepen

1. click on the little icon Open JS Settings on the JavaScript editor pane
2. Then add the following link under Add External Javascript

https://cdn.rawgit.com/serapath/e2b55cab315e60fbbffea7b43acd8749/raw/29aac6cb7361fb9d8467adee4e0d112961395a95/require.js

3. Press Save & Close and start using the require(...) in your JavaScript code on codepen

magnetikonline

List all Git repository objects by size

• Summary
• Example

Summary

Bash script to:

• Iterate all commits made within a Git repository.

nkint

import createRegl from 'regl'
import createCamera from 'regl-camera'
import bunny from 'bunny'
import normals from 'angle-normals'

const regl = createRegl()
const camera = createCamera(regl, {
  minDistance: 0.01,
  distance: 20,
  maxDistance: 30,

srdjan

100+ different js counter apps...

wclr

A way to handle state in cycle.js

Simple state management with xstream and ramda, in more transparent fashion than onionify

import * as R from 'ramda'

// first we create factory for making special state stream 
// that will hold our stream value and will be modified with supplied streams of reducers
type StateReducer<T> = (state: T) => T

anaisbetts

// Include this at the very top of both your main and window processes, so that
// it loads as soon as possible.
//
// Why does this work? The node.js module system calls fs.realpathSync a _lot_
// to load stuff, which in turn, has to call fs.lstatSync a _lot_. While you
// generally can't cache stat() results because they change behind your back
// (i.e. another program opens a file, then you stat it, the stats change),
// caching it for a very short period of time is :ok: :gem:. These effects are
// especially apparent on Windows, where stat() is far more expensive - stat()
// calls often take more time in the perf graph than actually evaluating the

Rich-Harris

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.

wegry

"use strict"

/*
 * Webpack 2 loader that can take CommonJS output by psc 0.9.1 and convert 
 * it into tree shakable ES6 modules. No transpiling required. 
 */
const fs = require('fs')

const commonJsRequire = /var ([$\w]+) = require\("(.*)"\)/g
const moduleExports = /module\.exports = \{(\n(    ([$\w]+): ([$\w]+)(, )?\n)*)?\};/m

briancavalier

import { readFile } from 'fs'

// Create a stream-returning version of fs.readFile
const readFileS = fromNode(readFile)

// Use it to create a stream containing the files contents
// map(String) to convert Buffer to string
const s = readFileS('./a/file.txt').map(String)

// Observe the contents