shaimo
shaimo
Yes, I installed node-read 0.1.6. I probably should have mentioned that I'm actually using it in the browser with browserify. I used node-readability before and wanted to try node-read instead...
@bndr let me try. Looking into the calling stack I see the following: ``` var readability = require('node-read'); // In my file | var cheerio = require('cheerio'); // In node_modules/node-read/index.js../lib/utils.js...
I updated to 0.1.7 but it didn't seem to update anything about cheerio. npm ls cheerio yields: ``` └─┬ [email protected] └── [email protected] ``` In any case still getting the same...
I don't think it's got to do with browserify - if I replace node-read with node-readability everything works just fine. I guess I'll stick with node-readability in the meantime... Thanks...
I'm not calling it directly. My server side is rails and I use the gem browserify-rails. Seems to work nicely as it allows me to write complex javascript with support...
ok, tried it. Loads ok with node-readability but still getting an error with node-read, albeit a different one. Here is the error and "calling stack": ``` Uncaught TypeError: Cannot read...
I think 9.0.7 is what I have installed globally but as part of my project I have ``` └── [email protected] ``` So I think it is ok. I tried to...
Was just a sudo missing. Updated global browserify to 12.0.1 but still getting same error when requiring node-read...
Any other insight as to how to debug with prerender:true. I'm getting an error but there is no indication whatsover where it comes from so I really don't know what...