Fix NPM release

[tomwayson]

At first I was noticing that after running npm install angular-esri-map all that I would see under node_modules/angular-esri-map is index.html and bower_components - wat???

See: https://twitter.com/tomwayson/status/666988609560539136

So I ran npm publish and now after running npm install angular-esri-map I get a blank folder.

Ugggggggggggggghhhhhhhhhhh!!!

[tomwayson]

the plot thickens

npm installs are indeed installing files on other machines. Blank folder above was related to issue in my env (which uses npm link).

However, there is no dist folder in the install. That is why this doesn't work:

https://npmcdn.com/[email protected]/dist/angular-esri-map.js

But this does:

https://npmcdn.com/[email protected]/src/core/esriLoader.js

However, since I'm using roughly the same build script as esri-leaflet, I'd expect these to fail:

https://npmcdn.com/[email protected]/dist/esri-leaflet.js
https://npmcdn.com/[email protected]/dist/esri-leaflet.js

But they work.

[tomwayson]

Furthermore, the dist folder and all files are in that release on GH:

https://npmcdn.com/[email protected]/src/core/esriLoader.js

[tomwayson]

Booyah - I think it's this:

https://docs.npmjs.com/misc/developers#keeping-files-out-of-your-package

Need to try adding a an .npmignore file. Looks like the way esri-leaflet does it is by including everything that .gitignore has except dist.

[tomwayson]

Should be fixed in 8f60281. Need to publish a new version to test.

[tomwayson]

Looks like RC2 release didn't include the dist folder either. I can't figure out why? It wasn't even on my local file system after running the release script (which errored out as usual).

[tomwayson]

For future reference, the second issue (dist folder not on local file system or in release) was due to gulp build being run in the gh-release branch. It needs to be run a second time after the script switches back to the master branch just before publishing.