search

akdubya / dustjs

Asynchronous templates for the browser and node.js
http://akdubya.github.com/dustjs/
MIT License
1.44k stars 131 forks source link

Update for node 0.6.x #39

Open caolan opened 12 years ago

caolan commented 12 years ago

require.paths has been removed in node 0.6.x, I've commented out the unshift call, but I'm not sure what purpose that line was serving. If the unshift call is essential you may need to find a way to modify the NODE_PATH and spawn a new process instead...

Baggz commented 12 years ago

+1

kmiyashiro commented 12 years ago

+1

bermi commented 12 years ago

+1

djcas9 commented 12 years ago

+1

dinedal commented 12 years ago

+1

kmiyashiro commented 12 years ago

You guys do know that this project is probably dead so someone should maintain a fork instead?

analytically commented 12 years ago

+1

fauzias commented 12 years ago

It's a great nice awesome project, why it shall be dead? anyone can pinpoint any maintaned fork?

funston commented 12 years ago

With require.paths commented out, seeing this error:

node.js:201 throw e; // process.nextTick error, or 'error' event on first tick ^ TypeError: Cannot call method 'runInNewContext' of undefined at Object.loadSource (/Users/rich/dev/node_modules/dust/lib/server.js:13:19)

g13n commented 12 years ago

Apart from commenting out/removing the require.unshift line, the following change is needed:

-Script = process.binding('evals').Script; +Script = require("vm");

Filirom1 commented 12 years ago

This issue is 5 months old. Is this project dead ?

kmiyashiro commented 12 years ago

https://github.com/linkedin/dustjs

kethinov commented 12 years ago

Is LinkedIn's fork basically the canonical version of dust.js now that the original can't run on current node?

g13n commented 12 years ago

Yes it can't. There's an API change after 0.4 that breaks the original version. Also the original is no longer being maintained, you should be using the LinkedIn version which is in active development.

fijiaaron commented 12 years ago

can you update the npm script to pull dust.js from linkedin if that is official now?