Chris Baldelomar

Results 11 comments of Chris Baldelomar

http://anniebowendesign.com/portfolio/item/birchgrove-cottage-1/

Thanks for your feedback. I will look into this. I know this is a common complaint that people have.

Happening all on the server side. I read in HTML from an API. I parse the content like so: ```js const html = parse(content, options); ``` My options are defined...

Even this is producing the error for me: ```js const options: HTMLReactParserOptions = { replace(domNode) { function test(node: any) { console.log(node); } test(domNode); }, }; const html = parse(content, options);...

Yes, I do get the same error when in the app directory. No error if in the pages directory. Here is my code in the app directory. layout.tsx ```js export...

https://github.com/webplantmedia/html-react-parser I just pushed a commit with the code. Thanks so much for looking into it! I have based a very big next js project in using this react parser....

Any insight on the nature of this error? Is it some new code procedure introduced in next js 15? If it is permanent, would I need to drop support of...

Sigh. I really needed to be able to loop inside other components. And keep it as a server component. Do you see this being a permanent move by nextjs 15...