Jean-Charles Sisk

Yup. Those are from: ``` $ docker run -d --name connectable \ -v /var/run/docker.sock:/var/run/docker.sock \ gliderlabs/connectable:latest ```

I also have resolvable, registrator, and consul running. Nothing is otherwise bound to 10000 anywhere.

That's the result of [this](https://github.com/gliderlabs/connectable/blob/f60fbdbedac37e2e00c1c35f0d772fd639968516/connectable.go#L44-L53), no?

Ah. My mistake. :grinning:

I threw together a sloppy, terribad, not OS-independent workaround while we wait for this one. ``` sh $ npx -q -p lodash -p @sisk/npx repl -e "console.log(require('lodash').VERSION)" 4.17.10 $ npx...

I've resolved this issue upstream (yeti) and submitted a [pull-request](https://github.com/yui/yeti/pull/19) to their team.

> More info ? Duplicate [this](https://github.com/krakenjs/confit/blob/59feac850a6dfb86ac524f4e14736f167ab215c1/lib/factory.js#L61) under [this](https://github.com/krakenjs/confit/blob/59feac850a6dfb86ac524f4e14736f167ab215c1/lib/factory.js#L46). That way, `import`s that exist on `env` and `argv` happen before that promise is considered resolved. Then, exposing something a little more...

That's totally clear. What I'm describing is a new lifecycle event. @aredridel and I were talking about the ability for modules to self-register in kraken. Having the ability to break...

Nice necrobump, @grawk.

I started working on a solution for this but I'm not totally satisfied. This is the solution I was working towards: ``` js config.set('a:b:c:d', 'newValue'); // emits 'a:b:c:d' with 'oldValue'...