We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
"elysia": "^1.1.4"
Linux 5.15.133.1-microsoft-standard-WSL2 x86_64 x86_64
Simply install @elysiajs/html as per the doc.
@elysiajs/html
import { Elysia } from "elysia"; import { html } from "@elysiajs/html"; new Elysia() .use(html()) .get( "/html", () => ` <html lang='en'> <head> <title>Hello World</title> </head> <body> <h1>Hello World</h1> </body> </html>` ) .get("/jsx", () => ( <html lang="en"> <head> <title>Hello World</title> </head> <body> <h1>Hello World</h1> </body> </html> )) .listen(30001);
No errors.
1 | (function (entry, fetcher) ^ SyntaxError: export 'Html' not found in '@kitajs/html'
Seems a version specific problem from @kitajs/html in their latest version 4.2.0, the following to the package.json fixes this issue for now.
@kitajs/html
4.2.0
package.json
"overrides": { "@kitajs/html": "4.1.0" }
The text was updated successfully, but these errors were encountered:
elysiajs/elysia-html#91 Probably should put the issue in the plugin repo
Sorry, something went wrong.
Bug workaround elysiajs/elysia#759
6ab5cba
Fix unnecessary as kitajs 4.2.1 fixes the issue.
Closing as kita 4.2.1 released
No branches or pull requests
What version of Elysia.JS is running?
"elysia": "^1.1.4"
What platform is your computer?
Linux 5.15.133.1-microsoft-standard-WSL2 x86_64 x86_64
What steps can reproduce the bug?
Simply install
@elysiajs/html
as per the doc.What is the expected behavior?
No errors.
What do you see instead?
Additional information
Seems a version specific problem from
@kitajs/html
in their latest version4.2.0
, the following to thepackage.json
fixes this issue for now.The text was updated successfully, but these errors were encountered: