dmnsgn

const listeners = (function listAllEventListeners() {
  let elements = [];
  const allElements = document.querySelectorAll('*');
  const types = [];
  for (let ev in window) {
    if (/^on/.test(ev)) types[types.length] = ev;
  }

  for (let i = 0; i < allElements.length; i++) {
    const currentElement = allElements[i];

nicohq

{
  "name": "browserify_babelify",
  "version": "1.1.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "watch": "watchify src/app.js -d -o bundle.js -v [ babelify --presets [es2015] ]",
    "build": "browserify src/app.js -t [ babelify --presets es2015 ] | uglifyjs -mco bundle.js"
  },

syafiqfaiz

1. Change your database RDS instance security group to allow your machine to access it.
   • Add your ip to the security group to acces the instance via Postgres.
2. Make a copy of the database using pg_dump
   • $ pg_dump -h <public dns> -U <my username> -f <name of dump file .sql> <name of my database>
   • you will be asked for postgressql password.
   • a dump file(.sql) will be created
3. Restore that dump file to your local database.
   • but you might need to drop the database and create it first
   • $ psql -U <postgresql username> -d <database name> -f <dump file that you want to restore>

• the database is restored

jiewmeng

'use strict';

/**
 * Starts `nodemon` and `browser-sync`
 */

const path = require('path');
const fs = require('fs');
const nodemon = require('nodemon');
const browserSync = require('browser-sync').create();

dragonjet

Step 1: Server Credentials

This assumes you are now connected to the server via SSH.

• sudo -s Enter root mode for admin access
• groupadd devgroup Create new group to be later granted access to /var/www/html

Creating a new Root User

• useradd -G root,devgroup masterdev Create new root user. Also add to the devgroup
• passwd masterdev Change password for the new root user
• At this point, you'll need to input your new root user's new password

jmar777

First, we need to figure out what the actual error is.  This is obviously frustrating given that the error message is intentionally truncating it.

1) SSH in to your node (various guides available for this if you're not already familiar with this).
2) Run this command (basically an Elastic Beanstalk wrapper command for npm install I found in a blog post [1]):
   $ sudo /opt/elasticbeanstalk/containerfiles/ebnode.py --action npm-install 2
3) Find the actual error message in the output from the npm install.

Once you know the error, it should hopefully be fairly obvious how to fix it.  I've run into two different errors over the last couple days on Elastic Beanstalk:

The first was a dependency that was using the new "^X.Y.Z" version syntax, which is only supported in Node >= v0.10.26 (whereas Elastic Beanstalk only supports up to v0.10.21 as of today).  The solution here was easy: hardcode a dependency version *prior* to when that dependency adopted to the new syntax.

gre

/*
 * This work is free. You can redistribute it and/or modify it under the
 * terms of the Do What The Fuck You Want To Public License, Version 2,
 * as published by Sam Hocevar. See the COPYING file for more details.
 */
/*
 * Easing Functions - inspired from http://gizma.com/easing/
 * only considering the t value for the range [0, 1] => [0, 1]
 */
EasingFunctions = {