Stack?

[samhstn]

What are we thinking in terms of frameworks?

I don't think that our technology choices will be any different than if we go for a web app, desktop app or chrome extension.

What to consider:

• Linting
• Testing frameworks/libraries
• Utility libraries
• Front end frameworks/bundlers
• CSS framework

[samhstn]

My thoughts:

Linting: I will be happy with any popular, strict, modern linting config. [Semi-]standard or airbnb are fine

Testing:

• Dom testing - karma is in my opinion the best choice out of karma, jasmine/qunit or nightwatch in so many ways.
• Frameworks - I would prefer using mocha as the runner with chai's expect assertion library as the testing framework over tape. It allows for more better grouping of tests and is more popular with more integration with other testing utilities (such as karma)
• If we have to do any spying/stubbing/mocking, I would go with sinon (because it's the only one I've used and it works)

Utility libraries:

• Ramda

Front end frameworks/bundlers:

• No frameworks (vanilla js)
• Rollup js for module loading

CSS framework:

• I've never used it, but Bulma looks nice and it's flexbox suits our modern browser usage

[Jbarget]

rather than using elm we could just use Ramda which @JMurphyWeb has a bit of familiarity with

[samhstn]

Thoughts on co for async stuff?

[Jbarget]

Havent used it before, is there a reason you want to use it over plain Promises? If its to learn it im all for it but just wondering if there was anything behind the suggestion

[samhstn]

So generators are supported in node 6+, chrome and firefox. They seem like a nice way to deal with async javascript (also I don't know very much about them, so I'd like to learn how to use their power).

The Co library provides methods to complement the generators syntax. A bit like the way bluebird offers some helpful utilities with promises.

Also it's really popular library (which is really small) and was created by tj