"server side rendering" is a misleading term since it implies there is a server. that isn't neccecarily the case here, since it supports running in the browser. I think "clover engine" is cute, short for "clover html rendering engine". Instead of "server side rendering", it's just rendering. This commit makes things a lot more concise, such as `ssr.ssrAsync` being renamed to `render.async` to play nicely with namespaced imports. `getCurrentRender` and `setCurrentRender` are just `current` and `setCurrent`, and the addon interface has been redesigned to force symbols with a wrapping helper.
20 lines
503 B
JSON
20 lines
503 B
JSON
{
|
|
"compilerOptions": {
|
|
"allowImportingTsExtensions": true,
|
|
"baseUrl": ".",
|
|
"incremental": true,
|
|
"jsx": "react-jsxdev",
|
|
"jsxImportSource": "#engine",
|
|
"lib": ["dom", "esnext", "esnext.iterator"],
|
|
"module": "nodenext",
|
|
"noEmit": true,
|
|
"outDir": ".clover/ts",
|
|
"paths": { "@/*": ["src/*"] },
|
|
"rootDir": ".",
|
|
"skipLibCheck": true,
|
|
"strict": true,
|
|
"verbatimModuleSyntax": true,
|
|
"target": "es2022"
|
|
},
|
|
"include": ["framework/**/*", "src/**/*"]
|
|
}
|