Hard time to build about aura HOT 25 CLOSED

I get similar errors (after removing lint) on windows:

M:\git\external\backbone-aura>grunt.cmd build
Loading "require.js" tasks and helpers...ERROR

Error: Cannot find module 'jsdom'

Running "clean:0" (clean) task

Running "requirejs:dir" (requirejs) task

Error: Missing either an "out" or "dir" config value. If using "appDir" for a
full project optimization, use "dir". If you want to optimize to one file,
use "out".
at Function.createConfig
(M:\git\external\backbone-aura\node_modules\grunt-contrib\node_modules\requir
ejs\bin\r.js:14946:19)
RequireJS failed. Use --force to continue.

Aborted due to warnings.

from aura.

Confirmed. These issues are my fault. Made a bunch of project restructures over the weekend and haven't updated the relevant build paths. This will be fixed soon.

from aura.

@gersongoulart Can this be closed?

from aura.

For me, after I manually install jsdom and xmlhttprequest, it hangs on jasmine. If I remove jasmine from the build task, it succeeds.

from aura.

Hey @neonguru, have you tried to download the latest and greatest and run npm install again before build? If not, please try to do so and let us know if you still encounter any problems? Thanks!

from aura.

Yes, that's what I did.

from aura.

Oh! @neonguru do you have PhantomJs installed? Make sure you got PhantomJS installed, which is a headless browser. Unfortunately PhantomJS cannot be installed automatically through grunt. See the grunt faq for installation instructions: https://github.com/cowboy/grunt/blob/master/docs/faq.md#why-does-grunt-complain-that-phantomjs-isnt-installed

Let me know if it works after installing PhantomJs?

I need to update Aura's documentation to explain that. Also maybe the jasmine task should not be part of the default task. What do you think @addyosmani?

from aura.

@neonguru Installing PhantomJS from brew is the easiest way to go.

@gersongoulart @addyosmani I managed to build Aura. However when I run grunt launch I'm getting this: __Error: ENOENT, stat '/Users/robert/Code/backbone-aura/index.html'_. Obviously it's a path error because it should point to [demo-build] directory instead of root of backbone-aura. But when I go to the right index.html file (manually) and I open it in Chrome/FF I'm getting the following error in dev console: Could not load module text!widgets/todos/templates/stats.html_unnormalized3,text!widgets/calendar/templates/base.html_unnormalized4,text!widgets/controls/templates/controls.html_unnormalized5,text!widgets/todos/templates/todos.html_unnormalized6

Also, is there any way working demo could be hosted somewhere on Aura wiki pages?

from aura.

For the last request. I meant to say somewhere on gh-pages... like a demo page perhaps :)

from aura.

Nvm guys... I figured it out. I also sent pull request (https://github.com/addyosmani/backbone-aura/pull/50)

from aura.

Isn't that done automatically bu grunt's default server task? https://github.com/cowboy/grunt/blob/master/tasks/server.js

from aura.

hmmm... not for me apparently. I saw it here https://github.com/cowboy/grunt/blob/master/docs/task_server.md

from aura.

Still getting the same error when I remove "base" setting from grunt.js config. (Error: ENOENT, stat '/Users/robert/Code/backbone-aura/index.html)

from aura.

I installed phantomjs and put it in my path (I can run it from the cmd line), but jasmine still displays the following and hangs:

Running specs for SpecRunner.html

from aura.

Haven't been able to confirm as it appears to be building for me. Anyone else?

from aura.

@neonguru Have you tried reinstalling your node environment? Try installing it from brew. Also did you run npm install with or without parameter -g? Try installing it with -d and make sure your local node_modules are up to date and there are no conflicts with global. Let us know.

You can always check build status here:
https://secure.travis-ci.org/#!/addyosmani/backbone-aura

from aura.

As I said, I'm on windows. Apparently that's the problem.

from aura.

Where do you want to go today? (tm)

Just kidding :). I'll try it on Monday at work, and I'll let you know.

On Saturday, July 14, 2012, Mark McKinney wrote:

As I said, I'm on windows. Apparently that's the problem.

---

Reply to this email directly or view it on GitHub:
https://github.com/addyosmani/backbone-aura/issues/41#issuecomment-6987860

Sent from iPhone

from aura.

Oh and give me more info. Node version, OS, etc...
Thanks

from aura.

Node 0.8.2
PhantomJS 1.6
Windows 7 Ultimate 64bit
=> Hangs on Jasmine, after displaying: Running specs for SpecRunner.html

Node 0.6.18
PhantomJS 1.4
Mint 13
=> Works fine

from aura.

It almost sounds like a compatibility problem of Phantom on Windows. I'll try to tet it out monday as well...

from aura.

Hey guys! I just tried Auras install and build in a Windows 7 Professional 32bit with NodeJS 0.8.3 and PhantomJS 1.6.0 and everything works as expected. So I'll consider this as a edge case problem with the environment, and not with our code, closing this issue. Please feel free to re-open or create a new issue if you find out there's any problem with Auras code.

from aura.

Same thing on Win XP. Everything worked just fine.

On Thursday, July 19, 2012, Gerson Goulart wrote:

Hey guys! I just tried Auras install and build in a Windows 7 Professional
32bit with NodeJS 0.8.3 and PhantomJS 1.6.0 and everything works as
expected. So I'll consider this as a edge case problem with the
environment, and not with our code, closing this issue. Please feel free to
re-open or create a new issue if you find out there's any problem with
Auras code.

---

Reply to this email directly or view it on GitHub:
https://github.com/addyosmani/backbone-aura/issues/41#issuecomment-7114251

Sent from iPhone

from aura.

Excellent. Thanks a lot for testing and verifying compatibility of the build, all!

from aura.

Still no go for me. Any tips on debugging Jasmine/PhantomJS?

I opened spec/SpecRunner.html and it says, "Passing 21 specs" in green (etc), but from grunt build, that's where it seems to hang. phantomjs is accessible from the command line. Is there a (sub) command I can run to see if things are working right?

from aura.