Alec Larson
Alec Larson
Using `import('/path/to/file.json')` should resolve with `{ default: }` instead of ``, or it won't match with what TypeScript infers.
Routes can't be declared (with `import(...)` function) from any module other than the `saus.routes` module. This is due to `compileNodeModule` being used on the route module, which means Vite plugins...
- Add `saus deploy new` to spin up a new deployment instead of updating - Add prompt to `saus deploy` that asks which active deployment to update, and if updates...
Currently, only the `saus/client` module has this power. Basically, isolated modules are reloaded on each request if they depend on `saus/client`, since its exports depend on the request. Other modules...
https://github.com/novemberborn/common-path-prefix/blob/master/index.js If multiple routes have the same route module, we can avoid duplication in client routes map. ```ts // Before export default { "default": "/assets/entry.8ae2ce2d.js", "/": "/assets/entry.8ae2ce2d.js", "/about": "/assets/entry.ba4aa235.js", }...
## The Problem There's no simple way to include code in client/server bundle only when a specific plugin/framework option has a specific value at build time. ### Example In any...
- All components are server-only when the nearest [route layout](https://github.com/alloc/saus/issues/70) has no `hydrator` defined. - For component subtrees to opt-in to client-side rendering, they need to attach some special `data-`...
Frontend developers are familiar with the concept of layouts, so let's align with that. This feature would replace the concept of "renderers" and the render module would be no more....
When a page is rendered, it produces its page-specific state module and any non-inlined state modules. These state modules need to be cached somewhere, so the server can respond to...