Last 12 weeks · 0 commits
2 of 6 standards met
Repository: developit/preact-markup. Description: :zap: Render HTML5 as VDOM, with Components as Custom Elements! Stars: 207, Forks: 27. Primary language: JavaScript. Languages: JavaScript (100%). License: MIT. Homepage: http://npm.im/preact-markup Topics: dom, html-renderer, jsx, markdown, markup, parse, preact, preact-components, xml. Latest release: 2.1.1 (5y ago). Open PRs: 7, open issues: 9. Last activity: 4y ago. Community health: 42%. Top contributors: developit, AkeemMcLennon, hpneo, marvinhagemeister, 38elements, arusanov, vpzomtrrfrt.
JavaScript
Hello, I'm facing _"preact-markup: Error: Document parse failed."_ error on passing with type as . Observed on preact-markup version 2.1.1. Codesandbox: https://codesandbox.io/s/preact-markup-issue-rjftnj Thanks
This might not be directly an issue, but I'm looking for some advice. I'm trying to use this package () in a Next.js codebase set up with as detailed in the using-preact example. I've also got TypeScript configured, with the following : I haven't followed the advice to add from the Preact TS docs as that causes hundreds of errors in our codebase. I'm guessing that would be beneficial in a 'pure' Preact codebase, but isn't useful here. (If you can confirm this hunch, that would be great). Now, the issue here is that, when I try to use `ElementClass@types/reactJSX.ElementClassMarkupconst Markup = BaseMarkup as any;` and call it a day, but I would like to find a way to accurately type this for my codebase, if at all possible so we can keep code completion in our editors. Is it possible to get this typed correctly somehow?
error TS1046: Top-level declarations in .d.ts files must start with either a 'declare' or 'export' modifier.