gro
gro copied to clipboard
task runner and toolkit extending SvelteKit 🌰 generate, run, optimize
Adds the `gen` plugin that defaults to watch mode. - [x] implement - [ ] how should the plugin work with `gro dev --no-watch` and `gro build`? Problem is `setup`...
For [historical reasons](https://github.com/feltcoop/gro/blob/main/src/docs/sveltekit.md) - not regrettable ones - Gro tries to do too much. SvelteKit and Vite came along and made the world beautiful again and now Gro no longer...
Gro has its own internal build system that originally was designed for TypeScript task support in user projects, and it uses filesystem paths hardcoded to Unix-style, so Windows just doesn't...
The [current SvelteKit integration](https://github.com/feltcoop/gro/blob/6f407c305ef1136c87a199264c3b03bb05eca74d/src/docs/sveltekit.md) overrides [`svelte-kit package`](https://kit.svelte.dev/docs/packaging), but we want Gro to do as little as necessary. Right now, tasks like [`gro build`, `gro deploy`, and `gro publish`](https://github.com/feltcoop/gro/blob/main/src/docs/build.md) duplicate some...
This has been a long time coming. Gro's build system is long gone, and it now uses a Node loader for TypeScript and Svelte, so it should be fairly easy...
todo - the build breaks when the SvelteKit project isn't built without adding `"target": "esnext",`, this is just a Gro problem right? - support Svelte 5 in the loader, something...
See these PRs where this was previously implemented, and then removed with the build system. - https://github.com/ryanatkn/gro/pull/283 - https://github.com/ryanatkn/gro/pull/382 Needs to be thought through in combination with Moss style optimizations....
see `https://github.com/oxc-project/oxc/issues/8369` and `https://github.com/oxc-project/oxc/issues/7788` todo - dynamic imports don't seem to be supported?
One of the few rough edges I notice often in Gro these days is the lack of types for `invoke_task`. - generate types so task name string+params are checked against...
[Oxc](https://github.com/oxc-project/oxc) is the future of SvelteKit and Vite, replacing [esbuild](https://github.com/evanw/esbuild) which has been good for my/Gro's usage. [Rolldown](https://github.com/rolldown/rolldown) will handle the server and worker bundling cases but it's not ready...