Generating component with loom generator breaks app

[eccegordo]

I am not sure if this is a bug in loom generators or ember-cli but the out of box experience for generating components seems to be broken. Using ember-cli 0.0.22 the following steps reproduce the issue.

ember new my-app

cd my-app

ember generate component x-foo

ember server
Livereload server on port 31929
Serving on http://0.0.0.0:4200


ENOENT, no such file or directory 'tmp/tree_merger-tmp_dest_dir-d8Mlx89P.tmp/appkit/tests/helpers/module_for.js' Error: ENOENT, no such file or directory 'tmp/tree_merger-tmp_dest_dir-d8Mlx89P.tmp/appkit/tests/helpers/module_for.js'
    at Object.fs.statSync (fs.js:684:18)
    ... snip ...
ENOENT, no such file or directory 'tmp/tree_merger-tmp_dest_dir-uMCHRsJT.tmp/appkit/tests/helpers/module_for.js' Error: ENOENT, no such file or directory 'tmp/tree_merger-tmp_dest_dir-uMCHRsJT.tmp/appkit/tests/helpers/module_for.js'
    at Object.fs.statSync (fs.js:684:18)
    ... snip ...

The offending code is in the generated test file

import { test , moduleForComponent } from 'appkit/tests/helpers/module_for';
import XFooComponent from 'appkit/components/x-foo';

comment out the above and ember server just works again.

[stefanpenner]

the loom generators are out of sync, we must address this soon.

@rpflorence hows loom doing?

[stefanpenner]

closing in favor of #351