-
Notifications
You must be signed in to change notification settings - Fork 5
Outdated version on NPM #38
Comments
0.0.4 and the current master (0.1.0-unstable) have very different APIs for plugins and I didnt want to put 0.1.0 on the NPM registry until I was happy it was stable and actually had some documentation. It was very, very briefly released, but I removed it within a small period of time due to a bug. 0.1.0 on the master branch in github should work, and does have most of the documentation written, so it should be useable. I'm been a little busy with work and family issues the last 3-4 months, so I've not done much with xi4n since then, however I think all thats left to do is just fix up livemap2.js, finish #33 and then release. Edit: After checking out the docs, they need to be finished being written as well :( |
Ok, no problem. I just thought, that there is someting wrong with npm. |
Sadly not :( I'm hoping to get put aside some time and finish off xi4n soon-ish. Patches still welcome, as always :) If you want to play with the master branch, but still want to use npm, you can run npm like this: But it won't auto-update :( Edit: If you guys think its stable as is I'm more than willing to publish it as is to just get an updated version out of the door. Sort of like a pre-release. |
I use another way: npm install -g git://github.com/theangryangel/XI4N.git and it works too! I saw somewhere that if you will use my method and you do npm update it will check for new version. But I'm not sure. You don't have to hurry so much. You did awesome work to this place and even 0.0.4 is great. |
I've just installed it manually, or as a drunker part of me has done in Windows.. Install it and then create alias to execute xi4n :p |
0.1.0 will be uploaded as soon as I'm back in the UK. Having some trouble pushing to npm from Australia atm =/ |
AUSTRALIA DOESN'T BELIEVE IN JAVASCRIPT! |
Hi!
When you install XI4N by npm you get 0.0.4 version which don't have many new features. Can you see what happened? I know that few days ago there were problems with npm, registry wan't working.
The text was updated successfully, but these errors were encountered: