Ender.js setup issues on Windows - getting npm WARN [email protected] error

Other Questions NPM
1

I’m having trouble getting Ender.js working on my Windows XP system. I followed the installation steps but running into some problems.

Here’s what I did:

  • Installed Node.js version 0.6.6
  • Got NPM version 1.1.0-beta-7 and extracted it
  • Used the Windows installation method as recommended

When I execute:

npm install ender -g

I get this warning message:

npm WARN [email protected] package.json: bugs['web'] should probably be bugs['url']

The basic ender commands seem to work (like ender help), but when I try to actually build a package it fails:

ender build jeesh
installing packages: "ender-js jeesh"...
this can take a minute...
something went wrong trying to load npm!

Any ideas what might be causing this npm loading issue? Would really appreciate some help getting this sorted out.

2

That npm warning about [email protected] won’t break anything - it’s just a package.json metadata issue. You’re probably running old versions of Node.js and NPM. I’ve hit this same problem on Windows XP. When you get “something went wrong trying to load npm,” it’s usually permissions or PATH issues. Try a complete NPM reinstall and make sure your PATH includes the npm directory. Also check that your Windows account can write to the global node_modules folder. If you’re on a beta NPM version, that could cause compatibility issues - might want to downgrade to stable.

3

That Node.js 0.6.6 and NPM 1.1.0-beta-7 combo is a known problem on Windows XP. I hit this exact issue about a year ago. The “something went wrong trying to load npm” error happens because Ender can’t talk to your NPM installation properly. Since you’re on a beta NPM version, there are API changes that break Ender. Downgrade to NPM 1.0.104 - it plays much nicer with Ender on Windows. You could also install Ender locally in your project instead of globally. That dodges the permission headaches Windows XP loves to throw at global npm modules.

4

hey, i had similar probs before. clearing the npm cache usually does the trick. also, double-check your npm path. try running cmd as admin too, might help! just make sure nothing is blocking it.