Possible issue on Windows

[tlack]

First, I apologize of the shitty bug report I am about to give, but it took me a while to fight through a variety of problems with Node 0.6 + Express + Dust + Dust-X (originally tried Express-dust) and I didn't keep very clear records as I went.

Regarding the dust-x part: I think there may be some kind of path name issue on Windows and the cache check in dust-x.js around line 60. I changed it to this to get it all working:

          if (!(name in dust.cache)) {
                        var dls = dust.loadSource(dust.compile(src, name));
                        dust.cache[name] = dls;
                    }

I suspect that dust.loadSource updates dust.cache, but treats the filename differently due to the backslashes in the path name.

[laurie71]

Sorry for not responding sooner; I haven't touched this code in a while. It's entirely possible that Dust has changed its cache conventions in the meanwhile; or it could be a result of different file path separators as you suggest. If you can write a simple test case that shows the problem I can take a look, but I don't have easy access to a Windows dev environment so no promises... :-/