Skip to content

Instantly share code, notes, and snippets.

View snovakovic's full-sized avatar

Stefan Novaković snovakovic

  • Split 21000 Croatia
View GitHub Profile
@spikeheap
spikeheap / README.md
Last active May 24, 2017 07:59
The most basic ES6-polyfilled test setup I can come up with

Karma, Browserify & Babelify

Do you need Promises and other ES6 goodness. This will give you polyfills for your tests, and a working Karma, Browserify & Babelify setup.

Caveats

This example has been drawn up for this StackOverflow question. You probably want to polyfill Promises, etc. unless all your supported browsers already contain it. You probably also want to keep your compilation/babelification/browserification process the same between build and test. Fortunately you can (hint: common config can live in package.json), but that's outside of the scope of this Gist.

@cdjhlee
cdjhlee / zeromq_install.sh
Last active August 24, 2021 19:37
install zeromq in ubuntu 14.04
#!/usr/bin/bash
##############################################
#from http://zeromq.org/intro:get-the-software
##############################################
#get zeromq
wget http://download.zeromq.org/zeromq-4.0.5.tar.gz
#unpack tarball package
@branneman
branneman / better-nodejs-require-paths.md
Last active June 29, 2024 16:00
Better local require() paths for Node.js

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions