Our current configuration of babel for microservices is a bit hard-coded. We should respect the users .babelrc configuration / make babel configurable in the stack tool.

see: https://github.com/Stackvana/stack/blob/master/lib/compileServiceCode/babel/index.js#L7

I'm not personally using babel for development, so it any babel users can assist here, it would be much appreciated.

cc @

In what cases is it possible for https://docs.rs/codespan-reporting/0.6.0/codespan_reporting/term/fn.emit.html to return an error? I see that the error type is std::io::Error; is it guaranteed to be only if a write to the underlying WriteColor fails? Or are there other validations involving the Config / Files / Diagnostic that might trigger an error from term::emit?

Currently, this repo has a ton of missing snippets. For instance, there are 23 supported projects and 111 support languages. If you multiply those numbers together, there are potentially 2553 snippets in this collection. At this time, there are only 29

With 948032e8d1, we have a font set for cogent. Need to use it in my part of the docs.

Plasma currently allows _ for function parameter names, but this makes less sense with Plasma than something with clauses such as ML or Prolog. We should probably remove it simplifying the language. This will (for now) not provide a way for programmers to avoid unused argument warnings, but we can add other ways to suppress these.