martinkavik/seeder

Set up Seed app and start dev server by running one command

Seeder

---

NOTE:

New Seed/WASM bundlers have been developed before I was able to really start to work on this project so I recommend to use them instead:

• Trunk - WASM web application bundler for Rust.
• Web Bundler - Bundles a Seed SPA for publishing.

(They are also listed on the Seed Awesome list)

---

It provides simple tooling and a convention for creating single page apps, so you can focus on the cool thing you want to build! It will be a better alternative to seed-quickstart-webpack. Everything will be written in Rust.

WIP - support me to make the development faster ; I'll write announcement on Seed forum and chat once it's ready for beta testing (links on seed-rs.org).

seeder's Issues

Thoughts

1. I switched to seed-quickstart with cargo make watch and the only thing I miss is reload after compilation.
2. Because rust compiles slowly and I save files often, I quite often want to disable watcher and compile code explicitly.
   I like to think about this as follows: when I code I call cargo check via hotkey quite often from my editor (or use inline warnings/errors). When I'm satisfied I call cargo build again via hotkey and this is my F5.
3. Most of the time your web app will need to communicate to some backend server. For example I'm using rocket. It would be really nice if I could serve client via rocket somehow. So I only need to cargo run my server and it will automatically invoke/serve/proxy client via Seeder.

Components

I really like how the seed framework is starting to shape up and as you @MartinKavik are creating a cli tool for it, I decide to try and suggest something:

I quite love at the moment in Ember.js how components work and how code can be organized. Ember.js has a router, models, controllers, services, templates and components. Usually a controller or a component is paired with a template. If you then use an addon like ember-css-modules you can also have namespaced CSS (or SASS/LESS) associated with that component.

The main advantage of this structure is that you can create small independent modules that are self contained in the same folder. I would suggest a similar structure for components here:

|-- components
    |-- some-component-name
        |-- component.rs
        |-- view.rs
        |-- styles.sass

Do you think something like this would be doable or even a good idea?

I know this is kind of structure is not exclusive on ember.js but it really does wonders to organize your code base.

Tips for improvement from the old quickstart

seed-rs/seed-quickstart#11

Inspiration

• https://www.elm-spa.dev/
• https://github.com/lucamug/elm-starter
• https://phoenixframework.org/ + https://shankardevy.com/code/phoenix-live-reload/
• https://emberjs.com/
• https://dev.to/lucamug/elm-starter-a-tool-for-the-modern-web-53b1

Base path

Seeder should be able to serve the app from a non-root url to test a base path and routing.