Bogdan Chadkin

@rauanmayemir Thanks. I will ping you when it will be ready for testing.

@zindel I thought about providing apis like this ```js import { build, serve } from 'fpack'; build({ // options }) serve({ // options }) ```

Guys, I'm busy these days. It's better to somebody else take this issue. @shellscape would be great to have your experience in this.

Yeah, config is better. At least package.json field.

I like flow `ini` like format https://flow.org/en/docs/config/options/#toc-module-system-node-resolve-dirname-string

/cc @zindel @ulrikstrid

I use `--mock` flag to set configs with necessary options. Globals are always bad for isolation. `process.env.NODE_ENV` should be enough.

https://github.com/fastpack/fastpack/issues/80

Hi @jquense @taion what do you think about this?

I'm not really a fan of this convention anymore caz it's confused me a few times lately. Also tiny-warning uses console.warn which is kinda a breaking change. Though it's not...