Mark
Mark
@athul-22 thanks ping me once you merge/rebase or if you'd like me to do it, I can do it as well
@adamkoch the overrides worked, see https://github.com/lilboards/lilboards/pull/2180
Relates to https://github.com/remarkablemark/html-react-parser/issues/864
@jlarmstrongiv could this help? https://github.com/remarkablemark/html-dom-parser/issues/502
@jlarmstrongiv would you be interested in improving the README.md? Since this feels more like an edge case, I think it makes more sense to make custom overrides in the bundler...
Could you clarify what you mean by adding an export? Do you mean this: ```js import 'html-dom-parser/server'; ```
Gotcha that might be a bit tricky to propagate since `html-dom-parser` relies on the bundler to figure out if the library uses the server parser or the browser parser.
@ElSeniorMikael can you help provide a [reproducible example](https://codesandbox.io/s/html-react-parser-z0kp6)?
I can confirm that I can reproduce the issue in https://codesandbox.io/p/sandbox/html-react-parser-864-0v3xvs This bug is coming from [html-dom-parser](https://github.com/remarkablemark/html-dom-parser)
@ElSeniorMikael can you do this as a workaround? ```js const text = "toto \r\n toto" parse(text.replace(/\r/g, "\n")) ``` Or: ```js const text = "toto \r\n toto" parse(text.replace(/\r|\n/g, "")) ``` See...