| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
fix: various types (#747) | 6 个月前 | |
fix: keep ripple.config.ts out of the client bundle (#1513) * fix: compile nested `module` namespaces instead of a `module server` error (#1505) `module A.B` parses as nested TSModuleDeclarations, and the parser sets `declare` only on the outermost one. The analyzer treated every non-declare `module` declaration as a submodule, so the inner part of `declare module A.B` and a `module` block inside `declare namespace` hit the fatal "`module server` can only be declared at the module level" error, even in loose mode, which discarded the file's Volar output. A submodule is now a `module` declaration outside any `declare` ancestor that is not the inner part of a dotted name. The name check runs before the level check, so the message names what the source wrote. A dotted `module server.api` reports that dotted names are not supported, and the module-level error is collected in loose mode like the others. The client and server transforms share one `is_server_module_declaration` that also requires a top-level declaration with a block body, so the forms the analyzer reports stay namespaces instead of being lowered. References to a `module` binding only count as submodule references when the binding is in the module scope, so `typeof B.x` inside `declare namespace A` no longer reports "Import submodule exports before using them". Fixes #1505 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix: keep ripple.config.ts out of the client bundle The generated hydration entry imported the whole config, so anything the config imported (middlewares and their server-only dependencies) was bundled for the browser and could throw before hydration, leaving the page inert. The entry now imports only the modules the config names for the client, and the server sends the matched route's entry and layout in `__ripple_data`. `transport` and `rootBoundary.pending`/`catch` take module references (a root-relative path or an `[exportName, path]` tuple, like a route `entry`). The dev server and the generated production entry load those modules on the server; the dev client entry is regenerated when the config changes. The browser export condition, `config.js`, and the adapter browser stub existed only because the browser imported the config, so they are removed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> | 1 天前 | |
fix: keep ripple.config.ts out of the client bundle (#1513) * fix: compile nested `module` namespaces instead of a `module server` error (#1505) `module A.B` parses as nested TSModuleDeclarations, and the parser sets `declare` only on the outermost one. The analyzer treated every non-declare `module` declaration as a submodule, so the inner part of `declare module A.B` and a `module` block inside `declare namespace` hit the fatal "`module server` can only be declared at the module level" error, even in loose mode, which discarded the file's Volar output. A submodule is now a `module` declaration outside any `declare` ancestor that is not the inner part of a dotted name. The name check runs before the level check, so the message names what the source wrote. A dotted `module server.api` reports that dotted names are not supported, and the module-level error is collected in loose mode like the others. The client and server transforms share one `is_server_module_declaration` that also requires a top-level declaration with a block body, so the forms the analyzer reports stay namespaces instead of being lowered. References to a `module` binding only count as submodule references when the binding is in the module scope, so `typeof B.x` inside `declare namespace A` no longer reports "Import submodule exports before using them". Fixes #1505 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix: keep ripple.config.ts out of the client bundle The generated hydration entry imported the whole config, so anything the config imported (middlewares and their server-only dependencies) was bundled for the browser and could throw before hydration, leaving the page inert. The entry now imports only the modules the config names for the client, and the server sends the matched route's entry and layout in `__ripple_data`. `transport` and `rootBoundary.pending`/`catch` take module references (a root-relative path or an `[exportName, path]` tuple, like a route `entry`). The dev server and the generated production entry load those modules on the server; the dev client entry is regenerated when the config changes. The browser export condition, `config.js`, and the adapter browser stub existed only because the browser imported the config, so they are removed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> | 1 天前 | |
docs: remove lazy destructuring from homepage examples | 10 天前 | |
Version Packages (#1446) | 19 天前 | |
feat: vite build via adapters, etc. (#721) | 6 个月前 | |
Version Packages (#1446) | 19 天前 | |
feat: new website (#694) * new website * format fix * format fix --------- Co-authored-by: Michal Makowski <michal.makowski97@gmail.com> | 7 个月前 | |
feat: vite build via adapters, etc. (#721) | 6 个月前 | |
Move typescript-plugin to tsrx (#916) * Move typescript-plugin to tsrx * format | 5 个月前 | |
fix deployment | 6 个月前 | |
feat: new website (#694) * new website * format fix * format fix --------- Co-authored-by: Michal Makowski <michal.makowski97@gmail.com> | 7 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 6 个月前 | ||
| 1 天前 | ||
| 1 天前 | ||
| 10 天前 | ||
| 19 天前 | ||
| 6 个月前 | ||
| 19 天前 | ||
| 7 个月前 | ||
| 6 个月前 | ||
| 5 个月前 | ||
| 6 个月前 | ||
| 7 个月前 |