yoavniran

The Ultimate Unit Testing Cheat-sheet

---

• Sinon Chai
• Chai
• Sinon

krnlde

"use strict";
import fs from 'fs';
import express from 'express';
import bodyParser from 'body-parser';
import Handlebars from 'handlebars';
import wkhtmltopdf from 'wkhtmltopdf';

const app = express();

app.use(bodyParser.json());

reneviering

var chai = require('chai');
var expect = chai.expect;
var sinon = require('sinon');
var sinonChai = require('sinon-chai');
chai.use(sinonChai);



var eventBus = (function () {
	var _eventHandler = null;

ashleygwilliams

Hello!

You've published a series of packages that depend on all packages in the npm registry, probably using this program: https://github.com/Ell/npm-gen-all

We’re not entirely sure what your motivations are for creating this series of packages, but we have some concerns.

First, these packages violate npm's Terms of Use. Much like a squatter package, these have no individual functionality beyond depending on other packages. As a result, we intend to remove them from the registry this afternoon.

It seems that these series of packages might be a response to the events of last week and recent changes to our unpublish policy. A few community members are concerned that series of packages like the ones you’ve created will make unpublishing packages completely impossible after the 24 hour window. This is not the case. These series of packages are not valid package dependents because they violate th

wesbos

# Put this in your .zshrc or .bashrc file
# Install `tree` first — brew install tree
function t() {
  # Defaults to 3 levels deep, do more with `t 5` or `t 1`
  # pass additional args after
  tree -I '.git|node_modules|bower_components|.DS_Store' --dirsfirst --filelimit 15 -L ${1:-3} -aC $2
}

brennanMKE

React Native Trouble

Updating to macOS Sierra is causing trouble with React Native due to some of the Node.js and system utilities it uses. Specifically the watch utility fails due to a limit on the number of files which can be opened at a time.

The following command shows the current limit.

launchctl limit maxfiles

mischah

*.3ds filter=lfs diff=lfs merge=lfs -text
*.3g2 filter=lfs diff=lfs merge=lfs -text
*.3gp filter=lfs diff=lfs merge=lfs -text
*.7z filter=lfs diff=lfs merge=lfs -text
*.a filter=lfs diff=lfs merge=lfs -text
*.aac filter=lfs diff=lfs merge=lfs -text
*.adp filter=lfs diff=lfs merge=lfs -text
*.ai filter=lfs diff=lfs merge=lfs -text
*.aif filter=lfs diff=lfs merge=lfs -text
*.aiff filter=lfs diff=lfs merge=lfs -text

tuxBurner

How to migrate an existing repo to a lfs repo.

The tool can be found here.

https://github.com/bozaro/git-lfs-migrate/releases

I recommend to migrate an existing repo to a new repo with lfs support activated and delte the old one afterwards.

Requirements

facundofarias

# Install mutt using brew
$ brew install mutt

# Configure mutt
$ vim ~/.muttrc

# Put the following on the mutt config file (.muttrc)
set imap_user = “YOUR_USERNAME@GMAIL_OR_YOUR_DOMAIN.com”
set imap_pass = “YOUR_PASSWORD”
set smtp_url = “smtp://YOUR_USERNAME@[email protected]:587/”

AshikNesin

import React from 'react'
import axios, { post } from 'axios';

class SimpleReactFileUpload extends React.Component {

  constructor(props) {
    super(props);
    this.state ={
      file:null
    }