Closed OClement closed 10 years ago
Correction:
using require('jade')
would load a browser version if I understand correctly, as it contains a ref to the window
object.
The correct file to load is actually require('./lib/index')
For some reason, when comparing a normal installation of Jade through NPM, the target file is indeed ./lib/jade.js
while the version packaged with ss-jade
still refers to the same path, but ./lib/jade.js
was renamed to ./lib/index.js
Hi,
Apologies for the long time before responding. Is this issue still occurring today?
Regards,
Paul Jensen
Hi Thanks for taking the time to respond despite the long delay Unfortunately I wouldn't be able to tell; I changed my mind over a few things and ended up not using this I haven't tried this since that time, sorry!
Hi,
No worries. I'll mark this issue as closed for now, as I haven't been able to replicate it. If it occurs again, I'll be on hand to fix it.
Using ss-jade like so (app.js) :
ss.client.formatters.add(require('ss-jade'));
Yields this error open launching the app:
Referring to:
Shouldn't it be
... : require('jade');
?Not sure what JADE_COV is or what it reffers to, might need modifications as well.
Actually I'm not sure this issue is directly related to ss-jade, but since jade was working fine for me in express without using socketstream...