These are mostly equivalent, but `import *` has some restrictions that `import ... = require` doesn&#39;t.

`import * as` creates an identifier that is a *module object*, emphasis on *object*. According to the ES6 spec, this object is never callable or `new`able - it only has properties. If you&#39;re trying to import a function or class, you should use

    import express = require(&#39;express&#39;);

or (depending on your module loader)

    import express from &#39;express&#39;;

Attempting to use `import * as express` and then invoking `express()` is always illegal according to the ES6 spec. In some runtime+transpilation environments this might happen to work anyway, but it might break at any point in the future without warning, which will make you sad.

    import * as express from &quot;express&quot;;

This is the suggested way of doing it because it is the standard for JavaScript (ES6/2015) since last year.

In any case, in your tsconfig.json file, you should target the module option to commonjs which is the format supported by nodejs.



I know we use `enumerate` for iterating a list but I tried it on a dictionary and it didn&#39;t give an error.

CODE:

    enumm = {0: 1, 1: 2, 2: 3, 4: 4, 5: 5, 6: 6, 7: 7}
    
    for i, key in enumerate(enumm):
        print(i, key)

OUTPUT:

    0 0
    
    1 1
    
    2 2
    
    3 4
    
    4 5
    
    5 6
    
    6 7

Can someone please explain the output?


enumerate() for dictionary in Python

Is there a built-in lodash function to take this:

	var params = [
		{ name: &#39;foo&#39;, input: &#39;bar&#39; },
		{ name: &#39;baz&#39;, input: &#39;zle&#39; }
	];

And output this:

	var output = {
		foo: &#39;bar&#39;,
		baz: &#39;zle&#39;
	};
	
Right now I&#39;m just using `Array.prototype.reduce()`:

	function toHash(array, keyName, valueName) {
		return array.reduce(function(dictionary, next) {
			dictionary[next[keyName]] = next[valueName];
			return dictionary;
		}, {});
	}

	toHash(params, &#39;name&#39;, &#39;input&#39;);
	
Wondering if there&#39;s a lodash short-cut.

lodash: mapping array to object

I am using TypeScript with Express/Node.js.

For consuming modules, the TypeScript Handbook shows the following syntax:

```
import express = require(&#39;express&#39;);
```

But also the `typescript.d.ts` file shows:

```
import * as express from &quot;express&quot;;
```

I also searched the MSDN blog but could not find anything.

Which one is more correct as of early 2016? What are the differences between the two, if any?

Where is the best source to find information on the latest syntax to use so I can find this information in the future?

TypeScript import/as vs import/require?

I am using TypeScript with Express/Node.js.
For consuming modules, the TypeScript Handbook shows the following syntax:
<pre><code class="hljs language-ini">import express = require('express');
</code></pre>
But also the <code>typescript.d.ts</code> file shows:
<pre><code class="hljs language-javascript">import * as express from "express";
</code></pre>
I also searched the MSDN blog but could not find anything.
Which one is more correct as of early 2016? What are the differences between the two, if any?
Where is the best source to find information on the latest syntax to use so I can find this information in the future?

I&#39;m struggling to find documentation or examples of implementing an upload progress indicator using [fetch](https://github.com/github/fetch). 

[This is the only reference I&#39;ve found so far](https://jakearchibald.com/2015/thats-so-fetch/), which states:

&gt; Progress events are a high level feature that won&#39;t arrive in fetch for now. You can create your own by looking at the `Content-Length` header and using a pass-through stream to monitor the bytes received.
&gt;
&gt; This means you can explicitly handle responses without a `Content-Length` differently. And of course, even if `Content-Length` is there it can be a lie. With streams you can handle these lies however you want.

How would I write &quot;a pass-through stream to monitor the bytes&quot; sent? If it makes any sort of difference, I&#39;m trying to do this to power image uploads from the browser to [Cloudinary](http://cloudinary.com/documentation/image_upload_api_reference).

**NOTE**: I am ***not*** interested in the [Cloudinary JS library](https://github.com/cloudinary/cloudinary_js), as it depends on jQuery and my app does not. I&#39;m only interested in the stream processing necessary to do this with native javascript and Github&#39;s `fetch` polyfill.

---
https://fetch.spec.whatwg.org/#fetch-api

Upload progress indicators for fetch?

I would like to close my login menu dropdown when the user click anywhere outside of that dropdown, and I&#39;d like to do that with Angular2 and with the Angular2 &quot;approach&quot;...

I have implemented a solution, but I really do not feel confident with it. I think there must be an easiest way to achieve the same result, so if you have any ideas ... let&#39;s discuss :) !

Here is my implementation:

# The dropdown component: #

This is the component for my dropdown:

- Every time this component it set to visible, (For example: when the user click on a button to display it) it subscribe to a &quot;global&quot; rxjs subject *userMenu* stored within the *SubjectsService*.
- And every time it is hidden, it unsubscribe to this subject.
- Every click anywhere **within** the template of this component trigger the *onClick()* method, which just stop event bubbling to the top (and the application component)

Here is the code

    export class UserMenuComponent {

        _isVisible: boolean = false;
        _subscriptions: Subscription&lt;any&gt; = null;

        constructor(public subjects: SubjectsService) {
        }

        onClick(event) {
            event.stopPropagation();
        }

        set isVisible(v) {
            if( v ){
                setTimeout( () =&gt; {
    this._subscriptions =  this.subjects.userMenu.subscribe((e) =&gt; {
                           this.isVisible = false;
                           })
                }, 0);
            } else {
                this._subscriptions.unsubscribe();
            }
            this._isVisible = v;
        }

        get isVisible() {
            return this._isVisible;
        }
    }

# The application component: #

On the other hand, there is the application component (which is a parent of the dropdown component):

- This component catch every click event and emit on the same rxjs Subject (*userMenu*)

Here is the code:

    export class AppComponent {

        constructor( public subjects: SubjectsService) {
            document.addEventListener(&#39;click&#39;, () =&gt; this.onClick());
        }
        onClick( ) {
            this.subjects.userMenu.next({});
        }
    }

# What bother me: #

 1. I do not feel really comfortable with the idea of having a global Subject that act as the connector between those components.
 2. The **setTimeout**: This is needed because here is what happen otherwise if the user click on the button that show the dropdown:
  * The user click on the button (which is not a part of the dropdown component) to show the dropdown.
  * The dropdown is displayed and **it immediately subscribe to the userMenu subject**.
  * The click event bubble up to the app component and gets caught
  * The application component emit an event on the **userMenu** subject
  * The dropdown component catch this action on **userMenu** and hide the dropdown.
  * At the end the dropdown is never displayed.

This set timeout delay the subscription to the end of the current JavaScript code turn which solve the problem, but in a very in elegant way in my opinion.

If you know cleaner, better, smarter, faster or stronger solutions, please let me know :) !


How can I close a dropdown on click outside?

I have the following code and I get the error &#39;Duplicate Declaration query_url&#39;.

      switch(condition) {
        case &#39;complex&#39;:
          const query_url = `something`;
          break;
        default:
          const query_url = `something`;
          break;
      }

I understand that query_url is getting declared twice which isn&#39;t right. But i don&#39;t know how to resolve this. Can someone please help on what should be the correct way to make this work?

Error Duplicate Const Declaration in Switch Case Statement

With regard to these great two sources: [NZakas - Returning Promises in Promise Chains](https://github.com/nzakas/understandinges6/blob/master/manuscript/11-Promises.md#returning-promises-in-promise-chains) and [MDN Promises](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise), I would like to ask the following:

Each time that we return a value from a promise fulfillment handler, how is that value passed to the new promise returned from that same handler?

For instance,

    let p1 = new Promise(function(resolve, reject) {
        resolve(42);
    });
    
    let p2 = new Promise(function(resolve, reject) {
        resolve(43);
    });
    
    let p3 = p1.then(function(value) {
        // first fulfillment handler
        console.log(value);     // 42
        return p2;
    });
    
    p3.then(function(value) {
        // second fulfillment handler
        console.log(value);     // 43
    });

In this example, `p2` is a promise. `p3` is also a promise originating from `p1`&#39;s fulfillment handler. However `p2 !== p3`. Instead `p2` somehow magically resolves to `43` (how?) and that value is then passed to `p3`&#39;s fulfillment handler. Even the sentence here is confusing.

Could you please explain to me what exactly is going on here? I am totally confused over this concept.

Promise callbacks returning promises

I have a date object that I want to 

 1. remove the miliseconds/or set to 0
 2. remove the seconds/or set to 0
 3. Convert to ISO string

For example:

    var date = new Date();
    //Wed Mar 02 2016 16:54:13 GMT-0500 (EST)
    
    var stringDate = moment(date).toISOString();
    //2016-03-02T21:54:13.537Z

But what I really want in the end is 

    stringDate = &#39;2016-03-02T21:54:00.000Z&#39;



Remove Seconds/ Milliseconds from Date convert to ISO String

I&#39;m on Windows 10, with Node 5.6.0 and npm 3.6.0. I&#39;m trying to install angular-material and mdi into my working folder. **npm install angular-material mdi** errors with:

    +-- angular@1.5.0

    +-- UNMET PEER DEPENDENCY angular-animate@^1.5.0

    +-- UNMET PEER DEPENDENCY angular-aria@^1.5.0

    +-- angular-material@1.0.6

    +-- UNMET PEER DEPENDENCY angular-messages@^1.5.0 `-- mdi@1.4.57

    npm WARN enoent ENOENT: no such file or directory, open
    &#39;C:\Users\xxxxx\Desktop\ngClassifieds\package.json&#39; 

    npm WARN angular-material@1.0.6 requires a peer of
    angular-animate@^1.5.0 but none was installed. 

    npm WARN angular-material@1.0.6 requires a peer of angular-aria@^1.5.0
    but none was installed. 

    npm WARN angular-material@1.0.6 requires a peer of
    angular-messages@^1.5.0 but none was installed.

How do I resolve this to get AngularJS Material and MDI installed?

How do I fix the npm UNMET PEER DEPENDENCY warning?

I have the following function which I use to invoke a Lambda function from within my code.

However when I try to use it within a Lambda function, I get the following error: 

    AWS lambda undefined 0.27s 3 retries] invoke({ FunctionName: &#39;my-function-name&#39;,
      InvocationType: &#39;RequestResponse&#39;,
      LogType: &#39;Tail&#39;,
      Payload: &lt;Buffer &gt; })

How can I invoke a Lambda function from within a Lambda function?

My function:

    &#39;use strict&#39;;
    
    var AWS = require(&quot;aws-sdk&quot;);
    
    var lambda = new AWS.Lambda({
        apiVersion: &#39;2015-03-31&#39;,
        endpoint: &#39;https://lambda.&#39; + process.env.DYNAMODB_REGION + &#39;.amazonaws.com&#39;,
        logger: console
    });
    
    var lambdaHandler = {};
    
    // @var payload - type:string
    // @var functionName - type:string
    lambdaHandler.invokeFunction = function (payload, functionName, callback) {
    
        var params = {
            FunctionName: functionName, /* required */
            InvocationType: &quot;RequestResponse&quot;,
            LogType: &quot;Tail&quot;,
            Payload: new Buffer(payload, &#39;utf8&#39;)
        };
    
        var lambdaRequestObj = lambda.invoke(params);
    
        lambdaRequestObj.on(&#39;success&#39;, function(response) {
            console.log(response.data);
        });
    
        lambdaRequestObj.on(&#39;error&#39;, function(response) {
            console.log(response.error.message);
        });
    
        lambdaRequestObj.on(&#39;complete&#39;, function(response) {
            console.log(&#39;Complete&#39;);
        });
    
        lambdaRequestObj.send();
    
        callback();
    };
    
    module.exports = lambdaHandler;

Nodejs - Invoke an AWS.Lambda function from within another lambda function

I am currently developing a Node backend for my application. 
When dockerizing it (`docker build .`) the longest phase is the `RUN npm install`. The `RUN npm install` instruction runs on every small server code change, which impedes productivity through increased build time.

I found that running npm install where the application code lives and adding the node_modules to the container with the ADD instruction solves this issue, but it is far from best practice. It kind of breaks the whole idea of dockerizing it and it cause the container to weight much more.

Any other solutions?

How to cache the RUN npm install instruction when docker build a Dockerfile

The problem I have been struggling with for two weeks now while learning node.js is how to do synchronous programming using node. I found that no matter how I try to do things *sequentially* I always end up with nested promises. I have found that there are modules such as Q to help with promise chaining as far as maintainability.

What I don&#39;t understand while doing research is `Promise.all()`, `Promise.resolve()` and `Promise.reject()`. `Promise.reject` is pretty much self explanatory by the name but when writing an application I am confused on how to include any of these in functions or objects without breaking the behavior of the application.

There is definitely a learning curve to node.js when coming from a programming language such as Java or C#. The question that still resides is if promise chaining is normal (best practice) in node.js.

Example:

    driver.get(&#39;https://website.com/login&#39;).then(function () {
        loginPage.login(&#39;company.admin&#39;, &#39;password&#39;).then(function () {
            var employeePage = new EmployeePage(driver.getDriver());

            employeePage.clickAddEmployee().then(function() {
                setTimeout(function() {
                    var addEmployeeForm = new AddEmployeeForm(driver.getDriver());

                    addEmployeeForm.insertUserName(employee.username).then(function() {
                        addEmployeeForm.insertFirstName(employee.firstName).then(function() {
                            addEmployeeForm.insertLastName(employee.lastName).then(function() {
                                addEmployeeForm.clickCreateEmployee().then(function() {
                                    employeePage.searchEmployee(employee);
                                });
                            });
                        });
                    });
                }, 750);
            });
        });
    });

Are nested promises normal in node.js?

So in login page I am sending credentials from angular to express through get request.What I wanna do is that if found in database,send response and handle it in angular else if not found in db I want express to send error response and handle it angular error response function but my code isnt working.

Angular controller:
```
myapp.controller(&#39;therapist_login_controller&#39;, [&#39;$scope&#39;, &#39;$localStorage&#39;, &#39;$http&#39;,
  function($scope, $localStorage, $http) {
    $scope.login = function() {
      console.log($scope.username + $scope.password);
      var data = {
        userid: $scope.username,
        password: $scope.password
      };
      console.log(data);
      $http.post(&#39;/api/therapist-login&#39;, data)
        .then(
          function(response) {
            // success callback
            console.log(&quot;posted successfully&quot;);
            $scope.message = &quot;Login succesful&quot;;
          },
          function(response) {
            // failure callback,handle error here
            $scope.message = &quot;Invalid username or password&quot;
            console.log(&quot;error&quot;);
          }
        );
    }
  }
]);
```
APP.js:
```
  app.post(&#39;/api/therapist-login&#39;, therapist_controller.login);
```
Controller:
```
  module.exports.login = function(req, res) {

    var userid = req.body.userid;
    var password = req.body.password;
    console.log(userid + password);

    Credentials.findOne({
      &#39;userid&#39;: [userid],
      &#39;password&#39;: [password]
    }, function(err, user) {
      if (!user) {
        console.log(&quot;logged err&quot;);
        res.status(404); //Send error response here
        enter code here
      } else {
        console.log(&quot;login in&quot;);
      }
    });
  }
```


How to send error http response in express/node js?

I&#39;m trying to output all object list from database with sequelize as follow and want to get data are sorted out as I added id in where clause.

    exports.getStaticCompanies = function () {
        return Company.findAll({
            where: {
                id: [46128, 2865, 49569,  1488,   45600,   61991,  1418,  61919,   53326,   61680]
            },
            attributes: [&#39;id&#39;, &#39;logo_version&#39;, &#39;logo_content_type&#39;, &#39;name&#39;, &#39;updated_at&#39;]
        });
    };

But the problem is after rendering, all data are sorted out as follow.

    46128, 53326, 2865, 1488, 45600, 61680, 49569, 1418, ....

As I found, it&#39;s neither sorted by id nor name. Please help me how to solve it.

sequelize findAll sort order in nodejs

I am learning making Todo app.
On the website, I am studying is https://coderwall.com/p/4gzjqw/build-a-javascript-todo-app-with-express-jade-and-mongodb

I typed as instruction describes,

**app.js**
```js
var main = require(&#39;./routes/main&#39;);
var todo = require(&#39;./routes/todo&#39;);
var todoRouter = express.Router();
app.use(&#39;/todos&#39;, todoRouter);
app.get(&#39;/&#39;, main.index);
todoRouter.get(&#39;/&#39;,todo.all);
todoRouter.post(&#39;/create&#39;, todo.create);
todoRouter.post(&#39;/destroy/:id&#39;, todo.destroy);
todoRouter.post(&#39;/edit/:id&#39;, todo.edit);
```
**/routes/todo.js**
```js
module.exports ={
  all: function(req, res){
    res.send(&#39;All todos&#39;);
  },
  viewOne: function(req, res){
    console.log(&#39;Viewing &#39;+req.params.id);
  },
  create: function(req, res){
    console.log(&#39;Todo created&#39;);
  },
  destroy: function(req, res){
    console.log(&#39;Todo deleted&#39;);
  },
  edit: function(req, res){
    console.log(&#39;Todo &#39;+req.params.id+&#39; updated&#39;);
  }
};
```
and I got this error message

&gt; Error: Route.get() requires callback functions but got a [object
&gt; Undefined]

Did I miss something here?



Route.get() requires callback functions but got a &quot;object Undefined&quot;

I use Express-graphql middleware.
I send the following request in the body line:

    POST /graphql HTTP/1.1
    Host: local:8083
    Content-Type: application/graphql
    Cache-Control: no-cache
    Postman-Token: d71a7ea9-5502-d5fe-2e36-0ae49c635a29
    
    {
       testing {
          pass(id: 1) {
            idn
          }
        }
    }

and have error 

    {
      &quot;errors&quot;: [
        {
          &quot;message&quot;: &quot;Must provide query string.&quot;
        }
      ]
    }

in graphql i can send update in URL.

URL string is too short. i must send update model like

    mutation {
      update(id: 2, x1: &quot;zazaza&quot;, x2: &quot;zazaza&quot;, x3: &quot;zazaza&quot; ...(more more fields)...) {
        idn
      }
    }

i think its must be in request body. How can i send &#39;update&#39; query or that i&#39;m doing wrong?

Graphql post body &quot;Must provide query string.&quot;

I’m trying to add a property to express request object from a middleware using typescript. However I can’t figure out how to add extra properties to the object. I’d prefer to not use bracket notation if possible. 

I’m looking for a solution that would allow me to write something similar to this (if possible):&lt;br&gt;
    
    app.use((req, res, next) =&gt; {
        req.property = setProperty(); 
        next();
    });


Extend Express Request object using Typescript

I have some setup I want during a constructor, but it seems that is not allowed

[![no async const][1]][1]

Which means I can&#39;t use:

[![await][2]][2]


How else should I do this?

Currently I have something outside like this, but this is not guaranteed to run in the order I want?

    async function run() {
      let topic;
      debug(&quot;new TopicsModel&quot;);
      try {
        topic = new TopicsModel();
      } catch (err) {
        debug(&quot;err&quot;, err);
      }
    
      await topic.setup();


  [1]: http://i.stack.imgur.com/xUSOH.png
  [2]: http://i.stack.imgur.com/IIlGJ.png



async constructor functions in TypeScript?

I have this enum (I&#39;m using *TypeScript*) :

    export enum CountryCodeEnum {
        France = 1,
        Belgium = 2
    }

I would like to build a *select* in my *form*, with for each *option* the enum integer value as value, and the enum text as label, like this :

    &lt;select&gt;
         &lt;option value=&quot;1&quot;&gt;France&lt;/option&gt;
         &lt;option value=&quot;2&quot;&gt;Belgium&lt;/option&gt;
    &lt;/select&gt;

How can I do this ?


Select based on enum in Angular2

I&#39;m building a node app, and inside each file in .js used to doing this to require in various packages.

    let co = require(&quot;co&quot;);

But getting 

[![enter image description here][1]][1]

etc. So using typescript it seems there can only be one such declaration/require across the whole project? 
I&#39;m confused about this as I thought `let` was scoped to the current file.

I just had a project that was working but after a refactor am now getting these errors all over the place.

Can someone explain?


  [1]: http://i.stack.imgur.com/Dgrz2.png

Cannot redeclare block scoped variable

Is there any way to have a TypeScript enum compatible with strings from JSON? 

For example:

    enum Type { NEW, OLD }

    interface Thing { type: Type }
    
    let thing:Thing = JSON.parse(&#39;{&quot;type&quot;: &quot;NEW&quot;}&#39;);

    alert(thing.type == Type.NEW); // false

I would *like* `thing.type == Type.NEW` to be true. Or more specifically, I wish I could specify the `enum` values to be defined as *strings*, not numbers.

I am aware that I can use `thing.type.toString() == Type[Type.NEW]` but this is cumbersome and seems to make the enum type annotation confusing and misleading, which defeats its purpose. The JSON is technically *not* supplying a valid enum value, so I shouldn&#39;t type the property to the enum.

So what I am currently doing instead is using a string type with static constants:
    
    const Type = { NEW: &quot;NEW&quot;, OLD: &quot;OLD&quot; }

    interface Thing { type: string }
    
    let thing:Thing = JSON.parse(&#39;{&quot;type&quot;: &quot;NEW&quot;}&#39;);

    alert(thing.type == Type.NEW); // true

This gets me the usage I want, but the type annotation `string` is way too broad and error prone.

I&#39;m a bit surprised that a superset of JavaScript doesn&#39;t have string based enums. Am I missing something? Is there a different way this can be done? 

----------

**Update TS 1.8**

Using [string literal types][1] is another alternative (thanks @basaret), but to get the desired enum-like usage (above) it requires defining your values *twice*: once in a string literal type, and once as a value (constant or namespace):

    type Type = &quot;NEW&quot; | &quot;OLD&quot;;
    const Type = {
    	NEW: &quot;NEW&quot; as Type,
    	OLD: &quot;OLD&quot; as Type
    }
    
    interface Thing { type: Type }
    
    let thing:Thing = JSON.parse(`{&quot;type&quot;: &quot;NEW&quot;}`);
    
    alert(thing.type === Type.NEW); // true

This works but takes a lot of boilerplate, enough that I don&#39;t use it most of the time. For now I&#39;m hoping the [proposal for `string enums`](https://github.com/Microsoft/TypeScript/issues/1206#issuecomment-240581743) will eventually make the roadmap.

---------

**Update TS 2.1**

The new [`keyof` type lookup][2] allows for the string literal type to be generated from the keys of a const or namespace, which makes the definition a *little* less redundant:

    namespace Type {
        export const OLD = &quot;OLD&quot;;
        export const NEW = &quot;NEW&quot;;
    }
    type Type = keyof typeof Type;
    
    interface Thing { type: Type }
    
    const thing: Thing = JSON.parse(&#39;{&quot;type&quot;: &quot;NEW&quot;}&#39;);
    thing.type == Type.NEW // true


----------

**Update TS 2.4**

[TypeScript 2.4 added support for string enums][3]! The above example becomes:

    enum Type {
        OLD = &quot;OLD&quot;,
        NEW = &quot;NEW&quot;
    }
    
    interface Thing { type: Type }
    const thing: Thing = JSON.parse(&#39;{&quot;type&quot;: &quot;NEW&quot;}&#39;);
    alert(thing.type == Type.NEW) // true

This looks *nearly* perfect, but there&#39;s still some heartache:

* You *still* have to write the value twice, ie `OLD = &quot;OLD&quot;`, and there&#39;s no validation that you don&#39;t have a typo, like `NEW = &quot;MEW&quot;`... this has already bitten me in real code.
* There&#39;s some oddities (perhaps bugs?) with how the enum is type checked, its not just a string literal type shorthand, which is what would be truly correct. Some issues I&#39;ve bumped into:

        enum Color { RED = &quot;RED&quot;, BLUE = &quot;BLUE&quot;, GREEN = &quot;GREEN&quot; }
    
        type ColorMap = { [P in Color]: number; }
    
        declare const color: Color;
        declare const map: ColorMap;
        map[color] // Error: Element implicitly has an &#39;any&#39; type because type &#39;ColorMap&#39; has no index signature.

        const red: Color = &quot;RED&quot;; // Type &#39;&quot;RED&quot;&#39; is not assignable to type &#39;Color&#39;.
        const blue: Color = &quot;BLUE&quot; as &quot;RED&quot; | &quot;BLUE&quot; | &quot;GREEN&quot;; // Error: Type &#39;&quot;RED&quot; | &quot;BLUE&quot; | &quot;GREEN&quot;&#39; is not assignable to type &#39;Color&#39;.

    The equivalent code with `enum Color` replaced by string literal types work fine...

Yeah, I think I have OCD about this, I just want my perfect JS enums. :)


  [1]: https://github.com/Microsoft/TypeScript/wiki/What&#39;s-new-in-TypeScript#string-literal-types
  [2]: https://github.com/Microsoft/TypeScript/wiki/What&#39;s-new-in-TypeScript#keyof-and-lookup-types
  [3]: https://github.com/Microsoft/TypeScript/wiki/What&#39;s-new-in-TypeScript#string-enums

Typescript `enum` from JSON string

Angular provides life cycle hook `ngOnInit` by default.

Why should `ngOnInit` be used, if we already have a `constructor`?

Content Type	Original Author	Original Content on Stackoverflow
Question	Adam Thompson	View Question on Stackoverflow
Solution 1 - Javascript	Ryan Cavanaugh	View Answer on Stackoverflow
Solution 2 - Javascript	thitemple	View Answer on Stackoverflow

TypeScript import/as vs import/require?

Javascript Problem Overview

Javascript Solutions

Solution 1 - Javascript

Solution 2 - Javascript

lodash: mapping array to object

enumerate() for dictionary in Python

Attributions