Arnaud Rinquin ArnaudRinquin

To get a quick and dirty stack traces with Jasmine's HTML Reporter, add this on the spec runner page after jasmine/boot.js.

<script type="text/javascript" src="sourcemapped-stacktrace.js"></script>
<script type="text/javascript">
  jasmine.getEnv().addReporter({
    jasmineDone: function() {
      var traces = document.querySelectorAll(".jasmine-stack-trace")
      for(var i = 0; i < traces.length; i++) {
 (function(node){

Problem

While building a JavaScript single page app that acts as a front-end to multiple backend servers, even if they are on the same host as the web app - but on different ports, you come across CORS issues.

Solution

Use a simple node.js + hapi.js server to:

Serve your static single page app
Act as proxy to the backend servers

Essential JavaScript Links

I no longer mantain this list. There are lots of other very comprehensive JavaScript link lists out there. Please see those, instead (Google "awesome JavaScript" for a start).

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

Hey! I saw this has been indexed by the search engines. It is a first draft of a post I ended up publishing on my blog at: Scaling PostgreSQL With Pgpool and PgBouncer

Thanks for stopping by!

PostgreSQL and Pgpool Architecture

	* {
	font-size: 12pt;
	font-family: monospace;
	font-weight: normal;
	font-style: normal;
	text-decoration: none;
	color: black;
	cursor: default;
	}