.jsan packaging seems broken relative to recent npm and node.js versions

[michaelsbradleyjr]

Hi, Nickolay.

You may recall how in IRC I indicated a couple of weeks ago that installations of the most recent versions of node.js and npm, followed by installations of Joose-related packages, e.g. task-joose-nodejs, weren't accompanied by the expected ".jsan" files.

I tested this again yesterday; here are my steps:

1. create a new user on a freshly created linux vm
2. as the new user in its home directory run: git clone git://github.com/creationix/nvm.git ~/.nvm then . ~/.nvm/nvm.sh then nvm install v0.4.8 (these steps install nvm and npm together, latest versions)
3. run: npm install task-joose-nodejs

At this point a .jsan directory is nowhere to be found anywhere under ~/.nvm/v0.4.8. Just to make sure I wasn't missing something, with mlocate installed I ran sudo updatedb && locate jsan but it returned no results.

I'm filing this issue under your Dis-Zilla-Plugin-JSAN distro as it seems like it would be something related to post-install logic for packages created with dzil.

This isn't a critical issue for me as presently I'm working happily with node v0.4.5 and an older version of npm. But I wanted to bring it to your attention again as it certainly seems like a show-stopper for anyone looking to get started with cross-environment Joose-based libs. Maybe the problem is related to my installing node with nvm, but again the jsan-packaging has worked without any problems with node and npm installed via nvm, until the most recent releases of node and npm.