gigo6000

const critical = require("critical");

const baseUrl = "https://www.github.com";
const targetPath = "public/css/";
const dimensions = [
    {
        width: 320,
        height: 568,
    },
    {

nodkz

/* eslint-disable prefer-template */

const path = require('path');
const aliases = require('./aliases');

// ///////////////////////////////////////////////////////////////
// //////////////////   PLUGINS   ////////////////////////////////
// ///////////////////////////////////////////////////////////////

const commonPlugins = [

alekseykulikov

Recently CSS has got a lot of negativity. But I would like to defend it and show, that with good naming convention CSS works pretty well.

My 3 developers team has just developed React.js application with 7668 lines of CSS (and just 2 !important). During one year of development we had 0 issues with CSS. No refactoring typos, no style leaks, no performance problems, possibly, it is the most stable part of our application.

Here are main principles we use to write CSS for modern (IE11+) browsers:

• SUIT CSS naming conventions + SUIT CSS design principles;
• PostCSS + CSSNext. Future CSS syntax like variables, nesting, and autoprefixer are good enough;
• Flexbox is awesome. No need for grid framework;
• Normalize.css, base styles and variables are solid foundation for all components;

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.

markerikson

[02:06 PM] acemarke: @Steven : a couple other thoughts on the whole NODE_ENV thing. First, per my comments, it really is a Node concept. It's a system environment variable that Node exposes to your application, and apparently the Express web server library popularized using its value to determine whether to do optimizations or not
[02:08 PM] acemarke: Second, because of its use within the Node ecosystem, web-focused libraries also started using it to determine whether to they were being run in a "development" environment vs a "production" environment, with corresponding optimizations. For example, React uses that as the equivalent of a C #ifdef to act as conditional checking for debug logging and perf tracking. If process.env.NODE_ENV is set to "production", all those if clauses will evaluate to false.
Third, in conjunction with a tool like UglifyJS that does minification and removal of dead code blocks, a clause that is surrounded with if(process.env.NODE_ENV !== "development")

g0t4

From my Pluralsight course: https://app.pluralsight.com/library/courses/asynchronous-javascript-reasoning/table-of-contents

• Weather http://plnkr.co/edit/ZOAaSdtnfvR6WwiuVZ6s
• Avoid Blocking – Red Background http://plnkr.co/edit/z29VyH5BPvC4oc40EyOu
• setTimeout Pyramid Challenge http://plnkr.co/edit/DGiHFQOQfnipCcpex2RH
• Drag and Drop Red Box http://plnkr.co/edit/SmSpPS5ZgPvkgn8RE6y1
• Timer onReady http://plnkr.co/edit/gafgKCrxnDIJ6YaG9Jpx
• Timer measure http://plnkr.co/edit/kPOgzEuIvUmN4o6Jenem
• Progress Number Crunching - Web Worker https://plnkr.co/edit/Yy7BOZU9sIa8EyrxJwGH
• Event Listeners Are Synchronous http://plnkr.co/edit/mDvSHpF3HcTjtvltGmQn

danieldunderfelt

/* App creator */

import { extendObservable } from 'mobx'
import AppStore from '../app/AppStore'

export default (initialState = false) => {

  const stores = {
    App: AppStore
  }

yoavniran

The Ultimate Unit Testing Cheat-sheet

---

• Sinon Chai
• Chai
• Sinon

dudleystorey

// explanatory article: https://demosthenes.info/blog/993/1x-2x-3x-more-Batch-Processing-Retina-Images-with-PhotoShop-and-JavaScript

var inputFolder = Folder.selectDialog("Select a folder to process"),
outputFolder = Folder.selectDialog("Select a folder for the output files"),
imageSizes = [
    ["250px", "250px", "1x"],
    ["125px", "125px", "icon-2x"],
    ["75px", "75px", "icon-1x"]
],
numImageSizes = imageSizes.length;

ruandre

/***************************
 NOT MAINTAINED! from ~2015
****************************/

// photoshop script to resize images proportionally to fit inside a 1024px box i.e. longest side/edge will equal 1024px
// useful when scaling down many large photos for web use, simply toss in a batch action

var activeDoc = app.activeDocument
var docWidth = activeDoc.width
var docHeight = activeDoc.height