<commit_before># NodeJS library import example
Consumes [es2015-publish-template](https://github.com/setheen/es2015-publish-template) project using npm via github registry and [lodash](https://github.com/lodash/lodash) via npm

##Running this example
```sh
npm install
typings install
node app.js
```

## Mechanisms utilized
- npm
    - npm registry
- jspm
    - npm registry
    - github registry
- typings
    - lodash
    
## Scenario
Take a look at this image:
![](https://github.com/setheen/es2015-publish-template/examples/02_node_and_jspm/resources/jspm.png)


The key takeaway with this example is we are able to display intellisense module _"d.ts"_ declaration files within our IDE. 
For lodash, we can rely on the public _"typings"_ registry.  Simple enough right?  What about our own library project?

Stepping out of this example project, let's pretend we're about to publish our library for the world to consume.
We'd like to generate a d.ts definition file for coding ease.  Here are some popular options:

1. upload to [DefinitelyTyped](http://definitelytyped.org/tsd/) for eventual consumption via command _"tsd"_  
2. upload to [the typings registry](https://github.com/typings/registry) for eventual consumption via command _"typings"_
3. keep it within our source, exposed within package.json's _"typings"_ property

It turns out, option 1 is [deprecated](https://github.com/DefinitelyTyped/tsd) as mentioned [here](https://github.com/DefinitelyTyped/tsd/issues/269).<commit_msg>trying to center image<commit_after># NodeJS library import example
Consumes [es2015-publish-template](https://github.com/setheen/es2015-publish-template) project using npm via github registry and [lodash](https://github.com/lodash/lodash) via npm

##Running this example
```sh
npm install
typings install
node app.js
```

## Mechanisms utilized
- npm
    - npm registry
- jspm
    - npm registry
    - github registry
- typings
    - lodash
    
## Scenario
Take a look at this image:

<p align="center">
    <img src="resources/jspm.png"/>
</p>


The key takeaway with this example is we are able to display intellisense module _"d.ts"_ declaration files within our IDE. 
For lodash, we can rely on the public _"typings"_ registry.  Simple enough right?  What about our own library project?

Stepping out of this example project, let's pretend we're about to publish our library for the world to consume.
We'd like to generate a d.ts definition file for coding ease.  Here are some popular options:

1. upload to [DefinitelyTyped](http://definitelytyped.org/tsd/) for eventual consumption via command _"tsd"_  
2. upload to [the typings registry](https://github.com/typings/registry) for eventual consumption via command _"typings"_
3. keep it within our source, exposed within package.json's _"typings"_ property

It turns out, option 1 is [deprecated](https://github.com/DefinitelyTyped/tsd) as mentioned [here](https://github.com/DefinitelyTyped/tsd/issues/269).
{'fraction_non_alphanumeric': 0.09443507588532883, 'fraction_numerical': 0.012141652613827993, 'mean_word_length': 4.363471971066907, 'pattern_counts': {'":': 0, '<': 6, '<?xml version=': 0, '>': 6, 'https://': 11, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5545627', 'n_tokens_mistral': 912, 'n_tokens_neox': 834, 'n_words': 334}