Paul

Hello @perexg, > Sorry, it's probably the patch which introduced this issue (the write error code for the output file descriptor is handled differently than in the previous version). I...

second that. I'm trying to automate deployment using ansible. The way to work around this is * startup `hasura` (and `hbp`) excluding the config setting `HASURA_GRAPHQL_JWT_SECRET` * after `hbp` is...

The above only happens like described with the `--coffee` option. Skipping `--coffee` actually points to the root problem: the object literal in `.meteor-kitchen/templates/blaze/code/collection_shared_schema.js` has unescaped keys which prevents defining schema...

I understand that you keep the cli closed source until polished, but would you consider putting in this repo the distributed source stuff from `.meteor-kitchen`? I mean it's already distributed.

oh, and one other thing: i saw that there are 2 `object_utils.js` files: ``` ./templates/blaze/code/object_utils.js ./templates/react/code/object_utils.js ```

I just converted `/react/code/object_utils.js`on [js2.coffee](js2.coffee) and aside from the fact that this transpilation error remains it compiles. That being said i think it makes no sense to keep ES6 code...

OK, i really need this, and as i now found out, the package load order is - package - appcode - lib - other files/dirs - main - package startup...

@perak is there any chance of getting this in the next version? Basically it's just default copy directives for the two files and automatic write of the application.json into `packages/kitchen-settings/application.json`?

> The contacts_all query/publish function triggers the error. What I meant to say is that I attached an app for reproducing, and that the `"contacts_all"` publish showcases the behaviour. But...

I just realised that there is PR #6 . Have you looked into it?