Don't publish examples on npm

[vmx]

What is the time sink?

js-ipfs was publising examples which lead to huge download size due to publishing the dist folders of the examples. It got fixed here.

How do you think it can be solved?

I guess all projects should exclude the examples. If we agree on this all projects should be checked if they actually do it. Perhaps syncing the .npmignore files across repos.

How important do you think this is to fix?

Not urgent.

[jacobheun]

Should we look at just whitelisting our packages rather than dealing with the .npmignore blacklisting?

With most repos we'd be able to just add src and dist to the files property in package.json

"files": [
  "src",
  "dist"
]

The readme, license, changelog and package.json files will automatically be white listed. This would save us from random files that would be in peoples directories, such as editor files that .npmignore isn't covering. It's worth noting that .npmignore doesn't respect global git ignores.

[daviddias]

This looks like something the JS folks can handle with a script to update them all and a lint rule that checks for it. Sounds good? @alanshaw @achingbrain @vasco-santos @hugomrdias @jacobheun

[alanshaw]

+1 on a script to update them.

I have some half baked ideas about aegir doctor for detecting (and potentially fixing) things in your project that stray from aegir "best practices". This could be one of those things, but also things like having npm scripts for testing and release.

Also aegir create my-project which would spit out a aegir enabled template for building your new project with all of the best practices built in.

cc @hugomrdias