Can't install on Mac

[pixelshaded]

Using Mac OS X Version 10.7.5
Running

npm install jspm -g

Gives the following output:

npm ERR! notarget No compatible version found: traceur@'google/traceur-compiler#0.0.43'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["0.0.1","0.0.2","0.0.3","0.0.4","0.0.5","0.0.6","0.0.7","0.0.8","0.0.9","0.0.10","0.0.11","0.0.12","0.0.13","0.0.14","0.0.15","0.0.16","0.0.17","0.0.18","0.0.19","0.0.20","0.0.21","0.0.22","0.0.23","0.0.24","0.0.25","0.0.27","0.0.28","0.0.29","0.0.30","0.0.31","0.0.32","0.0.33","0.0.34","0.0.35","0.0.36","0.0.37","0.0.38","0.0.39","0.0.40","0.0.41","0.0.42","0.0.43","0.0.44","0.0.45","0.0.46","0.0.47","0.0.48","0.0.49"]
npm ERR! notarget 
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

npm ERR! System Darwin 11.4.2
npm ERR! command "node" "/usr/local/bin/npm" "install" "jspm" "-g"
npm ERR! cwd /Users/qabypass
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.14
npm ERR! code ETARGET
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/qabypass/npm-debug.log
npm ERR! not ok code 0

Looking at your packages json and this error, im wondering if the traceur dependency should be "0.0.43" instead of "google/traceur-compiler#0.0.43"

[guybedford]

This is strange since it is installing fine for me.

Have you verified your git ssh credentials on this machine?

I will post a new version shortly without this version format - it was needed when Traceur hadn't made an npm release yet.

Thanks for posting - these issues unreported are the things that kill projects.

[pixelshaded]

I'm pretty sure this failed then because I dont have git installed on the mac. I set up my SSH and it fails then on the git clone.

[guybedford]

So the npm install is still not working?

You do need git installed for jspm installs to work as well, so even when I post the traceur dependency fix this may still be an issue when using jspm.

Can you install git?

[pixelshaded]

My development machine is a windows machine. I was just going to test jspm on the mac while I waited for you to test it on windows. #53. I tried installing git with the osx installer but that has a bug. I then installed mac ports but the port command is not found. At that point I just gave up.

My main interest is the flattening of the packages since long paths have been making npm difficult to use in our windows CI environment.

[guybedford]

Note that jspm is designed for package management for the browser. jspm has interop with npm so far as packages run in the browser, but not currently a story for the server, and I'm not sure if an interop story for the server would make sense.

Windows support is definitely a high priority, and I'll be looking into the fix as soon as I can.

I'd advise testing out on Mac in the mean time if you can though.

[pixelshaded]

I'm using node more as a build tool than a server: compiling typescript and using the r.js AMD module optimizer. I'm using gulp for its tasks to simplify the process on our build server (which has deps on lodash which is where my huge node_modules tree comes from).

[guybedford]

jspm isn't going to help solve this unfortunately, as it is package management for the browser, not for NodeJS currently. I would suggest looking at npm dedupe, and I believe they are working on some improvements to this at the moment as well which should help you very soon.

[pixelshaded]

Your package was actually mentioned npm issue thread related to windows support: nodejs/node-v0.x-archive#6960 (comment)

[guybedford]

Yeah, it is only in relation to the browser though.

Perhaps we can look at NodeJS workflows for jspm in future (I mean, yes the loader does work on the server, but not too much thought has been put to environment detection for example), but the windows path limit is npm's problem to solve.

Things like NodeJS custom bindings etc wont' work either.

Also, we use the Node builtins from Browserify instead of the Node ones on the server, so we would need to update the builtin support.

It might be an option in future, thanks for bringing this up.

[briandipalma]

@pixelshaded Yep sorry I should have been clearer I mentioned it for "web apps", I didn't mean it for server side development.