r.js Windows pathing about r.js HOT 8 CLOSED

I believe I fixed this in #8, but please confirm by using the latest snapshot build, dist/r-20110726.js. Feel free to reopen this ticket if it does not fix the problem.

from r.js.

@drewwells: did you need to reopen this issue? I thought I got notification, but I cannot seem to find your comment now. I'll reopen the bug just in case, and if you can tell me the latest snapshot still fails with an error, I'll take a look.

I was responding to the part of the message above that mentions "Optimizer can only handle local paths. Download the locally if necessary and update the config to use a local path." and this was being incorrectly enforced for windows paths.

from r.js.

I uncovered an issue with my build profile and now realize it's broken on Windows and Linux. So I think the issue is unrelated, so I deleted it. It's only showing up while trying to build an optimized profile not in the 'dev' version.

I forget how proactive you are, I should have edited that the issue saying, coming back soon or not at all :)

from r.js.

So I finally figured out the problem, my build (possibly any build) is broken in v0.5.3pre of NodeJS. Not sure it's worth inspecting.
v0.4.10 works
v0.5.0 works
v0.5.1 works
v0.5.2 works
v0.5.3pre fails (Tag v0.5.2 on joyent/node)

from r.js.

I tried some build tests using Node 0.5.3 and they worked for me. However, what did not work was just running a requirejs-based app via node: node r.js main.js. I get this error:

Error: require.paths is removed. Use node_modules folders, or the NODE_PATH environment variable instead.

That pathway is not taken for a plain r.js -o optimization build though. If you still notice the error with 0.5.3, more info on the error and maybe a test profile (if different than above) might be helpful. I will look at fixing the error I see for plain app running in Node, but will do that as part of Issue #11.

from r.js.

Sorry looks like I'm still getting this issue with the windows built node available on their website, I'm working through the minGW instructions to see if that works on Windows.

from r.js.

You might try the latest snapshot, I have done some work since I last posted in this issue on improving windows support.

from r.js.

Yep that fixed this problem, thanks

from r.js.