bjrmatos

┐┌┐┌┐
┘└┘└┘\ₒ/
┐┌┐┌┐ ∕      Friday
┘└┘└┘ノ)
┐┌┐┌┐        deploy,
┘└┘└┘
┐┌┐┌┐        good
┘└┘└┘
┐┌┐┌┐        luck!
│││││

bjrmatos

// Disable javascript execution from console
// http://kspace.in/blog/2013/02/22/disable-javascript-execution-from-console/
var _z = console;
Object.defineProperty( window, "console", {
  get : function(){
    if( _z._commandLineAPI ){
      throw "Sorry, Can't exceute scripts!";
    }
    return _z; 
  },

bjrmatos

<?xml version="1.0" encoding="utf-8"?>
 
<configuration>
    <appSettings>
        
        <!-- Virtual Directory Setup
            assign virtualDirPath below a value like '/{path}'
            
            Add below to your app code and then prepend routes with virtualDirPath
            var virtualDirPath = process.env.virtualDirPath || ''; -->

bjrmatos

why ./task.js?

One word: task automation. It's basically zero effort and you can use the ./task.js package manager to handle any repetitive tasks. You can use ./task.js to automate everything with minimum effort.

./task.js provides the structure, order, and authority that you as a developer so desperately crave. ./task.js will also take responsibility for your actions if you need it to. It's what everybody is using now. ./task.js is the new hotness. It's all about ./task.js now, just like that.

This is compared to npm run/bash scripts, which are:

bjrmatos

function process(rule) { 
	if(rule.cssRules) { 
		for(var i=rule.cssRules.length-1; i>=0; i--) { 
			process(rule.cssRules[i]);
		}
	}
	if(rule.type == CSSRule.MEDIA_RULE) {
		if(window.matchMedia(rule.media.mediaText).matches) {
			rule.media.mediaText = "all";
		} else {

bjrmatos

var ref = require('ref');

module.exports = FixedString;

/**
 * Fixed length "String" type, for use in Struct type definitions.
 * Null-terminates by default.
 * Throws an Error if there's not enough space available when setting a string.
 */

bjrmatos

/** @flow */

require('./styles.css');
var React = require('react');
var {Link} = require('react-router');

var ignoreSplatRoutes = a => !/\*$/.test(a.path);
var ignoreDefaultRoutes = (a, b) => a !== b.defaultRoute;

var Toc = React.createClass({

bjrmatos

'use strict';

var AppDispatcher = require('../AppDispatcher');
var ActionTypes = require('../constants/ActionTypes');

var AuthActions = {
  signin: function(data) {
    AppDispatcher.handleViewAction({
      actionType: ActionTypes.AUTH_SIGNIN,
      data: data

bjrmatos

/* @flow */

var React = require("react")
var Immutable = require("immutable")

// In order to use any type as props, including Immutable objects, we
// wrap our prop type as the sole "data" key passed as props.
type Component<P> = ReactClass<{},{ data: P },{}>
type Element = ReactElement<any, any, any>

bjrmatos

repeat(a) -> [a]

Inspired by Haskell, I wanted to see if I could replicate, using ES6 features, the repeat function:

repeat :: a -> [a]

So as you can see in repeat.js, I have done exactly that. However there are some caveats.