Pierre-Eric Marchandet

Same stuff for `linter-ui-default` 😉 What's surprise me is that I don't get this issue on my setup... Anyway, shipping code in dev mode seems a bit... well... humm... anyway...

Q: Can I ask why meteor-helper has to change the current process's NODE_ENV? R: My users are using it to trigger different Meteor build. Q: Couldn't it just pass a...

Will do 😉 Pretty stoked on the fact that Atom's will be using React. Nice move 👍 EDITED: Well, Atom is getting back on React. Nice, nice, nice 😄

Thanks for the suggestion. Is it animated?

Sounds nice. I like the unified look and I would like to make Atom more "animated". I'll definitely have a look into it. Thanks again.

Sounds good to me: https://github.com/PEM--/meteor-helper/blob/master/lib/meteor-helper-view.coffee#L174 Try to set your path with the filename `deployments/test/settings.json`. You should be good to go.

Dawn! You're right. I'm reproducing it too. Seems like `meteor`'s command has changed its behavior. I only succeed into using absolute path.

Hi @thomasrivette, I don't own any Windows devices but some users have shared a solution for these environments: https://github.com/PEM--/meteor-helper#how-to-launch-meteor-on-windows-with-an-appropriate-path

It didn't work for you? Try to launch Meteor on the command line (the Console, if my memory serves me well). If it fails, you should find some help on...

If the command doesn't start, only the OS can trigger a log. When `meteor` is launched, it simply displays its log on the STDOUT and STDERR of the process that...