Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ember-cli 0.2.0: Could not find module appname/app #9

Closed
devinrhode2 opened this issue Mar 17, 2015 · 1 comment
Closed

ember-cli 0.2.0: Could not find module appname/app #9

devinrhode2 opened this issue Mar 17, 2015 · 1 comment

Comments

@devinrhode2
Copy link
Contributor

After upgrading to ember-cli 0.2.0 I got the error Could not find module appname/app with my app here: https://github.com/devinrhode2/major-domo/tree/95cfed62b88c29f07c5f4f7ef1580f43d668f390

Because this module was using the latest ember-cli-coffeescript when the error occurred, I had raised the issue there first: kimroen/ember-cli-coffeescript#70 but after switching all import/exports to escaped js, and swapping the modules, thing bug went away. This means that the bug lies within coffees6 and/or how it invokes ember-cli-coffeescript.

But, switching just app.coffee to the default ember-init generated app.js fixes the issue. router.coffee has no issues and doesn't need to be touched. Therefore, coffees6 actually does work with ember-cli 0.2.0, if app.coffee is converted to app.js. (Also, escaping the import/exports in app.coffee doesn't sold the issue, with or without semicolons, it needs to be fully converted to javascript)

So, I'm just going to keep doing everything normally but with an app.js instead of an app.coffee.

And to be clear, cat node_modules/ember-cli-coffees6/node_modules/ember-cli-coffeescript/package.json shows coffees6 is using v0.10.0 of ember-cli-coffeescript.

I'm extremely certain of these statements which you can verify yourself, and I hope this saves you debugging time! Since this module is already a hack, I think forcing users to do an app.js instead of app.coffee is more than acceptable, and we should instead focus efforts on making a more elegant solution to using import/exports in coffeescript.

@alexspeller
Copy link
Owner

This should be fixed now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants