Uncaught Error: Could not find module /app

[Nininea-zz]

I have updated ember-cli version, and after build application didn't load. my application name is 'scripts' and in verndor.js (ln.42) throws this error
"Uncaught Error: Could not find module scripts/app "
this is package.json

{
"name": "Scripts",
"version": "0.0.0",
"private": true,
"directories": {
"doc": "doc",
"test": "test"
},
"scripts": {
"start": "ember server",
"build": "ember build",
"test": "ember test"
},
"repository": "https://github.com/stefanpenner/ember-cli",
"engines": {
"node": ">= 0.10.0"
},
"author": "",
"license": "MIT",
"devDependencies": {
"body-parser": "^1.2.0",
"broccoli-asset-rev": "0.0.17",
"broccoli-ember-hbs-template-compiler": "^1.5.0",
"broccoli-merge-trees": "^0.1.4",
"broccoli-static-compiler": "^0.1.4",
"ember-cli": "0.0.40",
"ember-cli-ember-data": "0.1.0",
"ember-cli-ic-ajax": "0.1.1",
"express": "^4.1.1",
"glob": "^3.2.9",
"originate": "0.1.5"
}
}

this issue is very critical for me

[stefanpenner]

Unfortunately without steps to reproduce I'm unsure how to help.

I and many others have successfully upgraded and as such in unsure if this is actually a bug or user error.

[Nininea-zz]

It was defendecies problem. I fixed this bug, thanks

[alvincrespo]

@nininea What was the dependency issue that you came across? I'm also having the same problem.

[Nininea-zz]

added necessary 'values' in bower.json
this looks like so

{
...
"dependencies": {
"handlebars": "~1.3.0",
"jquery": "^1.11.1",
"qunit": "~1.12.0",
"ember-qunit": "~0.1.8",
"ember": "1.6.1",
"ember-resolver": "~0.1.5",
"loader": "ember-cli/loader.js#1.0.0",
"ember-cli-shims": "stefanpenner/ember-cli-shims#0.0.2",
"ember-load-initializers": "stefanpenner/ember-load-initializers#0.0.2",
"ember-qunit-notifications": "^0.0.3",
"ember-cli-test-loader": "rjackson/ember-cli-test-loader#0.0.2",
"bootstrap": "~3.2.0"
}
}

[alvincrespo]

Hmm. Yeah I've made sure my dependencies are up to date. But I'm getting the following error:

Uncaught Error: Could not find module cio/app

And it looks like its coming from this line in index.html:

window.Cio = require('cio/app')['default'].create(CioENV.APP);

I've also made sure to check that my environment configuration has APP configured correctly. Not sure what else to check?

[alvincrespo]

Hmm Looks like I need to implement this:

#1289

[stefanpenner]

seems like we need to be clearer about these sorts of changes. I thought the changelog would be sufficient but maybe not?

[jakecraige]

@stefanpenner I think that changelog is sufficient if people read through it, but it's riddled with bug fixes and addon dev only mixed with things that affect the user.

It would be nice if we could separate out changes that an end user would need to make to their app to upgrade. I think the changelog is still the place for this rather than maintaining another upgrade doc.

Just separating the changes that affect an end user from the others

[stefanpenner]

@jakecraige ya thats a good idea, we should split it into sections rather then 1 long list per release.

something like:

v0.0.41
=====

breaking changes:
* list
* of
* things

bugfixes:
* list
* of
* things

enhancements:
* list
* of
* things

cc @abuiles @rwjblue

[jakecraige]

Perhaps like so

0.0.40

Upgrading

• [BREAKING ENHANCEMENT] CoffeeScript support is now brought in by ember-cli-coffeescript. To use CoffeeScript with future versions run npm install --save-dev ember-cli-coffeescript (and broccoli-coffee is no longer needed as a direct dependency). [Coffee script support is provided by ember-cli-coffeescript addon. #1289]
• [BREAKING ENHANCEMENT] Move test only js/css assets into test-vendor.js and test-vendor.css respectively. [Test assets moved to test-vendor.js and test-vendor.css. #1288]
• [ENHANCEMENT] Update default Ember version to 1.6.0.
• [ENHANCEMENT] Tests now run with the "test" environment by default, config/environment.js contains an (empty) section for the "test" environment #1401
• [ENHANCEMENT] Update broccoli-asset-revto 0.0.17
• [ENHANCEMENT] Upgrade ember-qunit to 0.1.8. #1427

Else

• [BREAKING ENHANCEMENT] Rename test-vendor.{css,js} to test-support.{css,js} to better reflect its role. #1320
• [ENHANCEMENT] When using app.import to import non-js/css assets, you can now specify the destination of the asset. #1159
• [ENHANCEMENT] Display friendly error message when the server fails to start (e.g. address in use). #1306
• [ENHANCEMENT] EmberApp can take jshintrc path options for app and test jshintrc files. #1341
• [ENHANCEMENT] Using broccoli-sass > 0.2.0 now allows you to use .sass files. #1367
• [ENHANCEMENT] EmberAddon constructor to build an EmberApp object with defaults for addon projects. #1343
• [ENHANCEMENT] Allow addons to be vendored outside of node modules #1370
• [ENHANCEMENT] Make "ember version" show NPM and Node version (versions of all loaded modules with "--verbose" switch). #1307
• [ENHANCEMENT] EmberAddon constructor defaults process.env.EMBER_ADDON_ENV to "development". #
• [ENHANCEMENT] Add Git initialization to ember new command #1369
• [ENHANCEMENT] Addons can export an object instead of a function #1377
• [ENHANCEMENT] Addons will automatically load a generic addon constructor that includes app/vendor trees based on treesFor property if no main key is specified in package.json. #1377
• [ENHANCEMENT] Disable LOG_RESOLVER flag to reduce console.log noise by default. #1431
• [ENHANCEMENT] ExpressServer middleware extracted to addons that are always pulled into every Project first #1446
• [BREAKING BUGFIX] Standard variables passed in to Blueprints now handle slashes better. Breaking if you relied on the old behavior. #1278
• [BUGFIX] fix detection of static files to allow periods in urls #1399
• [BUGFIX] fix processing of import statements in css #1400
• [BUGFIX] fix detection of requests to be proxied #1263
• [BUGFIX] fix ember update (broken promises) #1265
• [BUGFIX] eagerly requireing inquirer was costing ~100ms -> 150ms on boot [https://github.com/stefanpenner/ember-cli/commit/0ae78df5b4772b126facfed1d3203e9c695e80a1)
• [BUGFIX] Fix issue with invalid warnings (regarding files in the root of vendor/) on Windows. #1264
• [BUGFIX] Fix addons being unable to use app.import to pull in non-js/css assets from their own vendor/ tree. #1159
• [BUGFIX] Fix issue with ember build failing if the public/ folder was deleted. #1270
  (Coffee script support is provided by ember-cli-coffeescript addon. #1289)
• [BUGFIX] Blueprint.prototype.normalizeEntityName's return value should update the entity name. #1283
  (Test assets moved to test-vendor.js and test-vendor.css. #1288)
• [BUGFIX] Store version check information correctly, and only change the lastVersionCheckAt timestamp when the version is checked from npm. #1323
• [BUGFIX] Update broccoli-es3-safe-recast to fix bugs with incorrectly replaced segments. #1340
• [BUGFIX] Duplicate-checking for generating routes now accounts for "-syntax. #1371
• [BUGFIX] Generating a route named 'basic' no longer adds it to router.js. #1390
• [BUGFIX] Fix pod based templates (was broken with the advent of the templates tree). #4138

[alvincrespo]

I think the CHANGELOG is definitely sufficient. But laying it out differently with breaking enhancements having its own section would definitely help out.

Thanks!

[jakecraige]

I do think that at least sorting them by what type of fix is important as well, I doubt we need headings for them. I like the idea of an upgrading section as most changes don't actually affect upgrading so separating those out seems good

[ccoenen]

👍 for Breaking at the top.

The only thing that could potentially be more important would be security-related fixes or fixes regarding data-loss, but this will probably both not be as huge a problem in this project.

[devinrhode2]

I have this error occurring after upgrading to ember-cli 0.2.0 and tracked it down to the coffees6 addon, which is a simple 64 line script here: https://github.com/alexspeller/ember-cli-coffees6/blob/master/index.js

You can read full details of the bug here: alexspeller/ember-cli-coffees6#9

But the coffees6 addon is a hack in the first place. I'm more concerned about seeing better separation of concerns between coffeescript and ecmascript, which would remedy these types of coffee-es.next issues for the long term.

[devinrhode2]

Important note: I find it rather strange that the coffees6 addon still completely works, and only fails when an app/app.coffee file is being used. I added a recommendation to use a plain app.js file instead.

(Any tips for debugging the root cause would be appreciated, I'm also down to pair up to help debug it)