ohmage / front-end

The repo for the 3.x browser front-end.
Apache License 2.0
1 stars 0 forks source link

Build issues with current node/npm #8

Open gicmo opened 9 years ago

gicmo commented 9 years ago

I am currently trying to build it on OS X (yosemite). It leads to the following error:

npm WARN package.json ember-cli-ic-ajax@0.1.0 No repository field.
npm ERR! Darwin 14.0.0
npm ERR! argv "node" "/usr/local/bin/npm" "install"
npm ERR! node v0.10.33
npm ERR! npm  v2.1.10
npm ERR! code E404

npm ERR! 404 Not Found: expresss
npm ERR! 404
npm ERR! 404 'expresss' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of 'ember-cli'
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

I guess it has something to do with node/npm version being of a newer version. I cooked up a docker container[1] with node 0.10.1 and npm 1.4.6 and then npm install & co worked but building it via ember build produced the following error:

root@92f9dc11e589:/home/ohmage# ember build
version: 0.0.37
Building...
object is not a functionTypeError: object is not a function
    at /home/ohmage/node_modules/ember-cli/lib/models/project.js:103:25
    at visit (/home/ohmage/node_modules/ember-cli/lib/utilities/DAG.js:23:3)
    at DAG.topsort (/home/ohmage/node_modules/ember-cli/lib/utilities/DAG.js:82:7)
    at Project.initializeAddons (/home/ohmage/node_modules/ember-cli/lib/models/project.js:90:9)
    at EmberApp._notifyAddonIncluded (/home/ohmage/node_modules/ember-cli/lib/broccoli/ember-app.js:110:16)
    at new EmberApp (/home/ohmage/node_modules/ember-cli/lib/broccoli/ember-app.js:106:8)
    at Object.<anonymous> (/home/ohmage/Brocfile.js:5:11)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.loadBrocfile (/home/ohmage/node_modules/ember-cli/node_modules/broccoli/lib/builder.js:147:14)
    at Class.module.exports.Task.extend.setupBroccoliBuilder (/home/ohmage/node_modules/ember-cli/lib/models/builder.js:15:26)
    at Class.module.exports.Task.extend.init (/home/ohmage/node_modules/ember-cli/lib/models/builder.js:32:10)
    at new Class (/home/ohmage/node_modules/ember-cli/lib/models/core-object.js:18:12)
    at Class.module.exports.Task.extend.run (/home/ohmage/node_modules/ember-cli/lib/tasks/build.js:18:19)
    at Class.module.exports.Command.extend.run (/home/ohmage/node_modules/ember-cli/lib/commands/build.js:22:22)
    at Class.Command.validateAndRun (/home/ohmage/node_modules/ember-cli/lib/models/command.js:74:15)
    at /home/ohmage/node_modules/ember-cli/lib/cli/cli.js:53:22
    at $$$internal$$tryCatch (/home/ohmage/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:470:16)
    at $$$internal$$invokeCallback (/home/ohmage/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:482:17)
    at /home/ohmage/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:1066:13
    at $$rsvp$asap$$flush (/home/ohmage/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:1531:9)
    at process._tickCallback (node.js:415:13)root@92f9dc11e589:/home/ohmage

Upgrading ember-cli to a newer version (0.0.44)

# ember build
version: 0.0.44
Build failed.
Path or pattern "vendor/ember-simple-auth/simple-auth.amd.js" did not match any files [string exception]
Error: Path or pattern "vendor/ember-simple-auth/simple-auth.amd.js" did not match any files [string exception]
[...]

I then upgraded the cli auth packages to 0.7.1 which resulted in:

root@92f9dc11e589:/home/ohmage# ember build
version: 0.0.44
Build failed.
Merge error: file "vendor/_loader.js" exists in /home/ohmage/tmp/custom_static_compiler-tmp_dest_dir-OzHELEan.tmp and /home/ohmage/tmp/custom_static_compiler-tmp_dest_dir-KhPSHsdT.tmp - pass option { overwrite: true } to mergeTrees in order to have the latter file win
Error: Merge error: file "vendor/_loader.js" exists in /home/ohmage/tmp/custom_static_compiler-tmp_dest_dir-OzHELEan.tmp and /home/ohmage/tmp/custom_static_compiler-tmp_dest_dir-KhPSHsdT.tmp - pass option { overwrite: true } to mergeTrees in order to have the latter file win
    at /home/ohmage/node_modules/ember-cli/node_modules/broccoli-merge-trees/index.js:49:21
    at $$$internal$$tryCatch (/home/ohmage/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:470:16)
    at $$$internal$$invokeCallback (/home/ohmage/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:482:17)
    at $$$internal$$publish (/home/ohmage/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:453:11)
    at $$rsvp$asap$$flush (/home/ohmage/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:1531:9)
    at process._tickCallback (node.js:415:13)

I guess I still don't have to correct mix of version for the various components. It would be great it you could maybe provide a pre-compiled package.

[1] https://gist.github.com/gicmo/abef9096d315fcbf2e90

ghost commented 9 years ago

Hi, I am having the same problem here. I spent the day trying different combinations of node.js and ember-cli in vain...

stevenolen commented 9 years ago

hi all!

Based on my knowledge of this particular front-end project, I believe it's a very early stage, potentially just a reference point for a future ohmage 3.0 frontend. The current stable branch of ohmage (2.16) uses a number of different frontend projects including: https://github.com/ohmage/gwt-front-end https://github.com/mobilizingcs/dashboard https://github.com/mobilizingcs/campaign_monitor

ghost commented 9 years ago

Thanks @stevenolen. I am not clear though on what you are suggesting to make this work... Cheers,

stevenolen commented 9 years ago

ah, sorry. I wasn't actually providing a suggestion for making it work...I don't anything about this particular project, just that the ohmage 3.0 server (what this frontend is coded against) is not a finished/complete version and this frontend is likely only partially developed based on that information. sorry I can't be of more help!

ghost commented 9 years ago

:-) No worries @stevenolen. Hopefully somebody will get back to us with an answer. The problem we are facing seems to be mostly related to the node and ember versions.

danielmconrad commented 9 years ago

Hey folks, I found this thread while doing a search for this same issue. I just noticed that the version of ember-cli that I'm using has an odd dependency for expresss here. The new version of ember-cli doesn't have this dependency. My guess is someone had a package on npm with that extra 's' that has been pulled from the registry. Fun times.