Workflow for managing dist files

[ananyaarun]

Description

Currently dist file are not in gitignore and hence huge lines of change needs to be merged in each PR. This leads to conflicts in dist files in other PR's etc. Dist files workflow are not very clear to a new comers and they usually get stuck with the grunt build step.

Solution

We can add dist to .gitignore
This has been done in IS repo here publiclab/image-sequencer#908

cc @sagarpreet-chadha @jywarren

[jywarren]

Oops, did we start gitignoring the .css files too? Yes, but we didn't stop tracking them. So, for some reason we aren't seeing dist files from NPM anymore. Huh? Let me look, maybe npm is reading our gitignore?

[jywarren]

Oops!

Use a .npmignore file to keep stuff out of your package. If there's no .npmignore file, but there is a .gitignore file, then npm will ignore the stuff matched by the .gitignore file. If you want to include something that is excluded by your .gitignore file, you can create an empty .npmignore file to override it.

So, ok i will override in this way. Opening a PR.

[jywarren]

#228