Support for Server Rendering?

[jaredpalmer]

No description provided.

[RafalFilipek]

Hey @jaredpalmer!
This might be hard while DomHandler from htmlparser2 package is async. Maybe there is some other way to parse with DomHandler (I couldn't find any sync way).
Other option is to switch to different library. Perfect scenario:

• synchronous parsing
• smaller size
• core node modules (like buffer) independent

[RafalFilipek]

@jaredpalmer checkout new 1.0.0 version. Should work with SSR :)
Let me know so I can close this issue.

[jaredpalmer]

Yes!!!! YOU ARE AWESOME!

import convert from 'jsxfromhtml/lib/convert'
...

function myPage ({html}) => (
  <div>
    {convert(html, {}, '', '')} 
  </div>
)

[RafalFilipek]

@jaredpalmer hmmm, why are you not using <JSXFromHTML /> component :) ?

[jaredpalmer]

Because https://github.com/RafalFilipek/jsxfromhtml/blob/master/src/index.js#L42 componentDidMount does not get called when you use ReactDOMServer.renderToString.

[jaredpalmer]

Also there is a weird issue with how you are declaring you module for npm. I use webpack on both server and client, and use ["babel-preset-env", { "modules: false" }] and also flow-syntax and strip-types on my own project. However, I get this error:

./~/jsxfromhtml/src/index.js
Module parse failed: /Users/jared/workspace/github/xxxxx/node_modules/jsxfromhtml/src/index.js Unexpected token (7:5)
You may need an appropriate loader to handle this file type.
| import convert from './convert';
| 
| type Props = {
|   html: string,
|   mapElements?: { [key: string]: any },
 @ ./common/screens/WP/Page.js 20:0-38
 @ ./common/routes.js
 @ ./client/Root.js
 @ ./client/index.js
 @ multi ./~/react-hot-loader/patch.js (webpack)-dev-server/client?http://0.0.0.0:5001 (webpack)/hot/dev-server.js ./client/index.js

If i comment out these lines from the package.json, everything works fine.

"module": "src/index.js",
  "jsnext:main": "src/index.js",

Thoughts?

[RafalFilipek]

Ad. SSR:
@jaredpalmer ohhh, right. Check this issue #4 out and let me now.

Ad. second problem ... looks like you have to parse jsxfromhtml with babel while webpack is looking for es6 code when module , jsnext:main is set. I'll create new issue for that and look at it ASAP.