What Template SHOULD be able to do

[gregglind]

Running list of the GUARANTEES you should get from using the template.

• All files lint
• testing
• dependency checks for all modules Doesn't catch missing, but code coverage does
• consistent package.json (fixpack)
• continuous integration <- TRAVIS ONLY
• shrinkwrap
• code coverage
• addon-linter
• nsp

[gregglind]

@pdehaan thoughts? Other contract? Add them if so!

[gregglind]

• depcheck still stinks.
• ci is unclear
• need to finish up tests for 100% coverage of the basic addon

[pdehaan]

Yeah, depcheck and similar are still awkward when we do things like require('chrome') and require('sdk') for add-ons stuff. https://github.com/mcasimir/depcheck-ci seems a bit better, but still uses depcheck under the hood.

Only other ones I could think of is integrating addons-linter and nsp.

[gregglind]

I claim all of these now work, for some values of work.

[gregglind]

Is it worth doing Circle CI and / or doing something different to catch the 'missing' keys?

Filed at: mcasimir/depcheck-ci#2

[gregglind]

TODO: update this bug for hte new template.

[motin]

These (except possibly dependency checking) are all covered in the new web extension based template.

[motin]

Closing since #73 is merged