Vajahath Ahmed vajahath

##How Homakov hacked GitHub and the line of code that could have prevented it

Please note: THIS ARTICLE IS NOT WRITTEN BY THE GITHUB TEAM or in any way associated with them. It's simply hosted as a Gist because the markdown formatting is excellent and far clearer than anything I could manage on my personal Tumblr at peternixey.com.

If you'd like to follow me on twitter my handle is @peternixey

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

Markdown License badges

Collection of License badges for your Project's README file.
This list includes the most common open source and open data licenses.
Easily copy and paste the code under the badges into your Markdown files.

Notes

The badges do not fully replace the license informations for your projects, they are only emblems for the README, that the user can see the License at first glance.

Translations: (No guarantee that the translations are up-to-date)

🇫🇷 Cette liste en français

How to build a VR CommLink with Google Daydream

Part 1: Making NASA style Radio Transmissions with the Tuna.js and WebAudio API

Recently, I had the chance to design a small audio module for a space-themed WebVR simulation.

Many people don't know that browsers support a remarkable set of tools for creating and transforming audio files.

We wanted our space simulation to be as immersive as possible. The user experience was all about communication. So we needed immersive audio to match our VR.

Let's see how we can create immersive audio for our interstellar radio transmissions, using only the browser!

Pure ESM package

The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.

This means you have the following choices:

Use ESM yourself. (preferred)
Use import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.
If the package is used in an async context, you could use await import(…) from CommonJS instead of require(…).
Stay on the existing version of the package until you can move to ESM.

	#!/bin/bash
	# Get postman app
	wget https://dl.pstmn.io/download/latest/linux64 -O postman.tar.gz
	sudo tar -xzf postman.tar.gz -C /opt
	sudo ln -s /opt/Postman/Postman /usr/bin/postman

	#Create a Desktop Entry
	cat > ~/.local/share/applications/postman.desktop <<EOL
	[Desktop Entry]
	Encoding=UTF-8

	// This file assures that a Jest test file and Cypress test file exists for each component.
	import path from "path";
	import fs from "fs";

	function getFiles(filepath: string) {
	return fs.readdirSync(filepath).filter(function (file) {
	return fs.statSync(path.join(filepath, file)).isFile();
	});
	}

	const CH_BRACE_L = 0x7b as const;
	const CH_BRACE_R = 0x7d as const;
	const CH_SQUARE_L = 0x5b as const;
	const CH_SQUARE_R = 0x5d as const;
	const CH_QUOTE_D = 0x22 as const;
	const CH_ESCAPE = 0x5c as const;
	const CH_COMMA = 0x2c as const;
	const CH_COLON = 0x3a as const;
	const CH_DOT = 0x2e as const;
	const CH_MINUS = 0x2d as const;

	var data = "do shash'owania";
	var crypto = require('crypto');
	crypto.createHash('md5').update(data).digest("hex");