https://github.com/yuryb/drex
drex is watching a module for updates and cleanly re-requires the module
after the update. New code is being require()d as if the new code is a
totally different module, so require.cache is not a problem.
var drex = require('drex');
... node code node code node code ...
// here goes my frea[ky/quently updated] piece of code, which lives in a js
file called mucode.js:drex.require('./mucode.js', function(mucode){
// at this point my mucode.js has been require()d, just like this:
// var mucode = require('./mucode.js');
// the code of the required module is the LATEST UPDATE TO mucode.js
mucode.muNewFunc(); });
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
