Narendra Sisodiya nsisodiya

## killByPort.sh
#!/usr/bin/env bash
kill `netstat -tulpn | grep :$1 | sed -e "s/.*LISTEN *//" -e 's/\/.*//'`

## .eslintrc
{
  "parser": "babel-eslint",
  "env": {
    "es6": true,
    "mocha": true,
    "node": true
  },
  "ecmaFeatures": {
    "blockBindings": true,
    "forOf": true,

## README.md

      
              1 file
            
          
              0 forks
            
          
              1 comment
            
          
              1 star
            
          
                boopathi
                / README.md
            
            
              Last active
              August 29, 2015 14:27
            
              
                Differentiate between an arrow function, class, method, generator and a normal function in ES6
              
          
    Moved to https://github.com/boopathi/functions-in-es6

  
## combining.js
// ------------
// counterStore.js
// ------------

import {
  INCREMENT_COUNTER,
  DECREMENT_COUNTER
} from '../constants/ActionTypes';

const initialState = { counter: 0 };

## alternative-to-higher-order-components.md

      
              1 file
            
          
              3 forks
            
          
              6 comments
            
          
              45 stars
            
          
                aldendaniels
                / alternative-to-higher-order-components.md
            
            
              Last active
              October 6, 2018 09:50
            
              
                Alternative to Higher-order Components
              
          
    React now supports the use of ES6 classes as an alternative to React.createClass().
React's concept of Mixins, however, doesn't have a corollary when using ES6 classes. This left the community without an established pattern for code that both handles cross-cutting concerns and requires access to Component Life Cycle Methods.
In this gist, @sebmarkbage proposed an  alternative pattern to React mixins: decorate components with a wrapping "higher order" component that handles whatever lifecycle methods it needs to and then invokes the wrapped component in its render() method, passing through props.
While a viable solution, this has a few drawbacks:

There's no way for the child component to override functionality defined on the higher order component.


## index.html
<html>
<body>
  <h1>Create an image/png blob, then fetch it with XHR</h1>
  <pre id="display"></pre>
  <script src="index.js"></script>
</body>
</html>

## anonymous
REPORT OF THE SANSKRIT COMMISSION 1956-57

Table of Contents


    INTRODUCTION
    HISTORICAL RETROSPECT
    THE PRESENT SITUATION

## Makefile
dist:
	browserify \
		--external lodash \
		--external moment \
		--require ./index.js:robot \
		> bundle.js
	cat umd-head.js bundle.js umd-tail.js > robot.js

## color1.scss
$boxwidth: 300px;
$boxheight: 200px;
$boxbackgroundcolor: #456343;
$whiteFontColor:#E3E1E1;
$bigFontsSize: 30px;
	#!/usr/bin/env bash
	kill `netstat -tulpn \| grep :$1 \| sed -e "s/.LISTEN //" -e 's/\/.*//'`
	{
	"parser": "babel-eslint",
	"env": {
	"es6": true,
	"mocha": true,
	"node": true
	},
	"ecmaFeatures": {
	"blockBindings": true,
	"forOf": true,
	// ------------
	// counterStore.js
	// ------------

	import {
	INCREMENT_COUNTER,
	DECREMENT_COUNTER
	} from '../constants/ActionTypes';

	const initialState = { counter: 0 };
	<html>
	<body>
	<h1>Create an image/png blob, then fetch it with XHR</h1>
	<pre id="display"></pre>
	<script src="index.js"></script>
	</body>
	</html>
	REPORT OF THE SANSKRIT COMMISSION 1956-57

	Table of Contents




	INTRODUCTION
	HISTORICAL RETROSPECT
	THE PRESENT SITUATION
	dist:
	browserify \
	--external lodash \
	--external moment \
	--require ./index.js:robot \
	> bundle.js
	cat umd-head.js bundle.js umd-tail.js > robot.js
	$boxwidth: 300px;
	$boxheight: 200px;
	$boxbackgroundcolor: #456343;
	$whiteFontColor:#E3E1E1;
	$bigFontsSize: 30px;