pintariching
pintariching
For the first thing, I think translating the compiler first would be a good idea. The original version can be found [here](https://github.com/sveltejs/svelte/tree/master/src/compiler). I think for now I'll write some steps...
I think a simple CLI is the last piece missing before doing a prerelease. I think it should just accept a file or a directory and call the `rustle::compile_file_to_js` function....
I think we can have a pre release when we get the parsing working. Also perhaps implementing a basic CLI with a few commands that you can point to a...
The latest library release adds support for nested component and passing properties to them. A lot of functionality still has to be tested by expanding the tests. Feel free to...
More tests would probably be a good idea. Maybe making a folder structure and having different files like `input.svelte`, `expected.js` and `output.js` in a folder for every test, then use...
`trunk` is a WASM web application bundler for Rust. I'd like to make `railwind` compatible with it, which should also add compatibility with a lot of Rusts UI frameworks, like...
- [x] #15 - [ ] #16 - [ ] #17 - [x] #18 - [ ] #19 If anything else comes to mind, I'll add it here.
Directives: - [ ] `@tailwind` - [ ] `@layer` - [ ] `@apply` - [ ] `@config` Functions: - [ ] `theme()` - [ ] `screen()` This should solve #4