Sung

> It's extensible and also allow to add mantra config or something else I agree but I am not sure if we need to store any config at this stage....

Sounds like an important feature. Some ideas: `mantra create --react-router` to create a new app with react router and save `router: react-router` to `mantra_cli.yaml`.

There are related issues https://github.com/mantrajs/mantra-cli/issues/43 and https://github.com/mantrajs/mantra-cli/issues/7. Feel free to join the discussion and PR is welcomed.

Looks like a bug in the release candidate for 0.4.0. Use [0.3.13](https://github.com/mantrajs/mantra-cli/releases/tag/v0.3.13) in the meantime.

@palpinter Updating `bebel-root-slash-import` will resolve the issue. See [here](https://talk.mantrajs.com/t/meteor-1-3-3-and-imports/360/8?u=sungwoncho). Can you check?

I've been working on `config` branch [here](https://github.com/mantrajs/mantra-cli/tree/config). Once released, this branch will allow users to customize templates. See [this comment](https://talk.mantrajs.com/t/do-we-have-to-use-the-mantra-generated-eslintrc/178/3?u=sungwoncho). We can make the default templates the same for both...

@macrozone I think that is one way to solve a problem. But @tomitrescak has been working on atom-package and I am not sure how he feels about such a drastic...

`undefined` is there because of a babel issue see https://github.com/meteor/meteor/issues/6281. It will be removed when the issue is resolved. Therefore it is not a high priority. You can still do...

There were definitely moments when I thought such feature would be useful. I suppose we can add a command: ``` mantra rename [type] [original name] [new name] ``` For each...

There is a [folk of this gem](https://github.com/wazery/ratyrate) that supports Rails 4.1.5.