Rahul Arya rahularyan

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

Social

Registration/Login

Ajax field validation (like phone number, email, password etc.)

Auto-deploying built products to gh-pages with GitHub Actions

This is a set up for projects which want to check in only their source files, but have their gh-pages branch automatically updated with some compiled output every time they push.

A file below this one contains the steps for doing this with Travis CI. However, these days I recommend GitHub Actions, for the following reasons:

It is much easier and requires less steps, because you are already authenticated with GitHub, so you don't need to share secret keys across services like you do when coordinate Travis CI and GitHub.
It is free, with no quotas.
Anecdotally, builds are much faster with GitHub Actions than with Travis CI, especially in terms of time spent waiting for a builder.

Theme Testing Process

from Theme Development (Wordpress Codex)

Fix PHP and WordPress errors. Add the following debug setting to your wp-config.php file to see deprecated function calls and other WordPress-related errors: define('WP_DEBUG', true);. See Deprecated Functions Hook for more information.
Check template files against Template File Checklist.
Do a run-through using the Theme Unit Test.
Validate HTML and CSS. See Validating a Website.
Check for JavaScript errors.
Test in all your target browsers. For example, IE7, IE8, IE9, Safari, Chrome, Opera, and Firefox.
Clean up any extraneous comments, debug settings, or TODO items.

	const express = require("express");
	const router = express.Router();

	router.get('/', function (req, res) {
	res.send("This is the '/' route in ep_app");
	});

	module.exports = router;

	// first set the body to hide and show everyhthing when fully loaded ;)
	document.write("<style>body{display:none;}</style>");

	jQuery(document).ready(function(){

	jQuery( 'input.search-field' ).addClass( 'form-control' );

	// here for each comment reply link of wordpress
	jQuery( '.comment-reply-link' ).addClass( 'btn btn-primary' );

	<?php
	class EmailTestCase extends PHPUnit_Framework_TestCase {

	/**
	* @var \Guzzle\Http\Client
	*/
	private $mailcatcher;

	public function setUp()
	{

	/**
	* Simple authentication and authorization example with passport, node_acl,
	* MongoDB and expressjs
	*
	* The example shown here uses local userdata and sessions to remember a
	* logged in user. Roles are persistent all the way and applied to user
	* after logging in.
	*
	* Usage:
	* 1. Start this as server

	#!/bin/bash

	# Following the guide found at this page
	# http://programmingarehard.com/2014/03/17/behat-and-selenium-in-vagrant.html

	echo "\r\nUpdating system ...\r\n"
	sudo apt-get update


	# Create folder to place selenium in

	User.aggregate([
	{
	/* Filter out users who have not yet subscribed */
	$match: {
	/* "joined" is an ISODate field */
	'subscription.joined': {$ne: null}
	}
	},
	{
	/* group by year and month of the subscription event */