rustle icon indicating copy to clipboard operation
rustle copied to clipboard

Svelte compiler rewritten in Rust

Results 16 rustle issues
Sort by recently updated
recently updated
newest added

Some options are: - [nom](https://github.com/geal/nom) - [chumsky](https://github.com/zesterer/chumsky) - [combine](https://github.com/marwes/combine) - [pest](https://lib.rs/crates/pest) `nom` and `pest` seem to be the most popular right now. Any other suggestions? Tell me what we should...

One place to start would be rewriting all the utilities from here: [https://github.com/sveltejs/svelte/tree/master/src/compiler/utils](https://github.com/sveltejs/svelte/tree/master/src/compiler/utils) A lot of them are used further up in the parsing and compiling. - [ ] clone.ts...

help wanted
good first issue

- [ ] decode_sourcemap.ts - [ ] index.ts - [ ] replace_in_code.ts - [ ] types.ts

- [ ] css - [ ] nodes - [ ] render_dom - [ ] render_ssr - [ ] utils - [ ] compiler_errors.ts - [ ] compiler_warnings.ts - [...

- [ ] read - [ ] state - [ ] utils - [ ] acorn.ts - [ ] errors.ts - [ ] index.ts

In `src/compiler/parse/utils/entities.rs`. `from_code` method matches duplicate two codes to both `Entity::nbsp` and `Entity::NonBreakingSpace`. It will cause the second statement to be never reached. 160 => Entity::NonBreakingSpace, 160 => Entity::nbsp,

Hi, I think we should use git conventional for our commit message and branch for easy maintenance. https://www.conventionalcommits.org/en/v1.0.0/

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...

Implemented a basic CLI, for now, that can compile any file with svelte syntax and a directory of files(has to end with either .svelte or .rustle).