Ryan Atkinson
Ryan Atkinson
I love this library, thank you!
This project was originally created as a mockup to communicate some ideas to people. It served its purpose well. It can go to pasture 🌄 it was a good mockup
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...
Followup - upgrade to Pixi 8 - https://pixijs.com/8.x/guides/migrations/v8