Does not work under Node 0.11.x and 0.12.x

[resistdesign]

When supplying a file that has a DIV as the outer most element I only get the DIV in the jade file and not any of it's children.

[resistdesign]

Seems to be an issue when running node 0.11.x.

[donpark]

Looks like most of the unit tests fails under Node 0.11.x with similar symtom (child nodes missing or truncated). Primary suspect is HTML parser or DOM implementation modules because html2jade outputs what it sees.

[skandasoft]

any updates on this

[donpark]

just tried with same result which is not surprising since jsdom-little hasn't changed.

do have to run html2jade under node 0.11.x?

[skandasoft]

I am trying to use this in latest chrome which I suppose has the latest node

[donpark]

sorry but chrome, the browser, does not have node.js inside of it.

[skandasoft]

with atom it does

[donpark]

Yes, Atom uses both Chrome and Node.js.
Have you tried running html2jade in the browser? See Programmatic Usage section of the README.md file for example. If you're using tools like browserify, you'll need to add jsdom-little module to the tool's list of modules to ignore.

[donpark]

TO THOSE WHO ABSOLUTELY NEED TO RUN HTML2JADE UNDER 0.11:

Try forking and replacing jsdom-lite dependency with jsdom. According to @zxdong262, this makes html2jade run under 0.11.x. Thx.

[paazmaya]

How about then switching away from jsdom-little completely and head over https://github.com/cheeriojs/cheerio?

[donpark]

Cheerio is definitely an option since jsdom-little appears to be abandoned. Only problem is I don't have a desperate need since I can just switch to Node.js 0.10 or use one of several web version. In other words, PR is welcome as long as backward compatibility is maintained to minimize backfire. :-)

[paazmaya]

Working in a PR.
Is there are use case when the library is used outside the Node.js context? Since there are things like this:

if module?
  isNode = true