-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
allow DOMParser to be passed in #18
Comments
Also, I noticed that Otherwise requiring |
This package is intended for client side, you might want vdom-to-html?
(From my phone)
… 在 2017年2月9日,05:32,Jannis Redmann ***@***.***> 写道:
Also, I noticed that vdom-parser implicitly relies on document to exist. Like with window.DOMParser, taking it as an optional parameter would be better.
Also, requiring global might be a good solution.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Nevertheless, it's a nice design goal to have isomorphic modules that both in the Browser and in Node. This makes Server-side rendering, tests and automation easier. This is why the Taking in an I tried |
It would be nice to be able to pass
DOMParser
intoparse
. Right now, I have to mutateglobal
in Node.js in order to be able to use this library.The text was updated successfully, but these errors were encountered: