Following on from my previous article, here is some more more useful information about the node.js implementation on webOS: the current version number and a list of supported modules:
events: EventEmitter, Promise
path: join, normalizeArray, normalize, dirname, filename, basename, extname, exists, existsSync
fs: Stats, readFile, readFileSync, close, closeSync, open, openSync, read, readSync, write, writeSync, rename, renameSync, truncate, truncateSync, rmdir, rmdirSync, fdatasync, fdatasyncSync, fsync, fsyncSync,mkdir, mkdirSync, sendfile, sendfileSync, readdir, readdirSync, fstat, lstat, stat, fstatSync, lstatSync, statSync, readlink, readlinkSync, symlink, symlinkSync, link, linkSync, unlink, unlinkSync, chmod, chmodSync, chown, chownSync, writeFile, writeFileSync, cat, catSync, watchFile, unwatchFile, realpathSync, realpath, createReadStream, ReadStream, FileReadStream, createWriteStream, WriteStream, FileWriteStream
child_process: spawn, fork, exec, execFile
http: STATUS_CODES, IncomingMessage, OutgoingMessage, ServerResponse, ClientRequest, Server,createServer, Client, createClient, cat
url: parse, resolve, resolveObject, format
net: Stream, createConnection, Server, createServer
querystring: unescape,escape, encode, stringify, decode, parse
crypto: createCredentials, Credentials, Hash, createHash, Hmac, createHmac, Cipher, createCipher, createCipheriv, Decipher, createDecipher, createDecipheriv, Sign, createSign, Verify, createVerify, RootCaCerts
dns: isIP, resolve, getHostByName, getHostByAddr, lookup, resolve4, resolve6, resolveMx, resolveTxt, resolveSrv, reverse, resolveNs, NODATA, FORMERR, BADRESP, NOTFOUND, BADNAME, TIMEOUT, CONNREFUSED, NOMEM, DESTRUCTION, NOTIMP, EREFUSED, SERVFAIL
dgram: Socket, createSocket
assert: AssertionError, fail, ok, equal, notEqual, deepEqual, notDeepEqual, strictEqual, notStrictEqual, throws, doesNotThrow, ifError
util: No
os: No
repl: writer, REPLServer, start
(The above is taken from a post by Ben Combee (@unwiredben) over at the – still locked – webOS SDK early access forums).
If you want to check the node.js version yourself in the future, shell into your Pre (either “novacom -t open tty://” in a terminal in linux or use novaterm in Windows) and enter “node –version”. At the time of writing I have confirmed that the current version is indeed 0.2.3.
Let’s hope that Palm get this upgraded to the latest version as soon as possible.
UPDATE: 2011/08 – For those who are interested it appears that the ‘string_decoder’ module is also available – handy to know when porting existing node modules to webOS.
