I upgraded my website recently and it's exciting! That being said, I admit my builds didn't get faster (they actually on average slowed down a bit). Hopefully that improves, but worth noting.
Astro 7.0
21–30 of 61 posts
Re: Astro 7.0
#22It's very cool to see the JS ecosystem reducing dependencies and I hope this trend continues.
Astro has gone from 247 deps in v6 to 190 in v7.
Re: Astro 7.0
#23It's very cool to see the JS ecosystem reducing dependencies and I hope this trend continues. Astro has gone from 247 deps in v6 to 190 in v7. https://node-modules.dev/#install=astro@7.0.6 https://node-modules.dev/#install=astro@6.0.0
This was actually part of the reason I made the Rust markdown processing, the unified ecosystem is a lot of deps!
I still have some plans in this area that should reduce the overall count further, though.
Re: Astro 7.0
#24Are these typical build speeds on static sites these days? It's slower than I expected for a rust re-write. (Or I guess maybe the portion re-written in rust is only a small part of the build pipeline time?)
My understanding is that astro isn't considered particularly slow?
Re: Astro 7.0
#25I made the Rust compiler and the Rust Markdown pipeline ( https://satteri.bruits.org ) in this, let me know if you have any questions, glad to answer anything!
Very cool! What was the trickiest part of coding Sätteri?
Re: Astro 7.0
#26Exhausting
because money
Re: Astro 7.0
#27Earlier quoted context omitted.
How does Satteri compare to a standard library like marked ( https://github.com/markedjs/marked )?
It depends in what regards you mean, I have some benchmarks here if you'd like to take a look at those: https://github.com/Princesseuh/web-markdown-benchmark The TL;DR is that `marked` is very light, but a bit on the slower side compared to Sätteri and `markdown-it` (and its forks). I'm not sure how friendly the extensibility is, but Sätteri re-use the same AST format as the unified ecosystem, which might feel more f…
We just use `marked` currently for some light markdown rendering in a game engine. This does look like it offers much better extensibility if we ever needed that - thanks for the clarity!
Re: Astro 7.0
#28I made the Rust compiler and the Rust Markdown pipeline ( https://satteri.bruits.org ) in this, let me know if you have any questions, glad to answer anything!
Very cool! What was the trickiest part of coding Sätteri?
It was tough to create a plugin API that was both performant and intuitive. Especially since the library people were migrating from (remark/rehype) was very laissez-faire in regard to the data you have access to, visiting patterns, etc.
Crossing data between Rust and JS is inherently kinda slow (relatively), so there's a constant push and pull between flexibility and performance that's not always easy to reason about!
Re: Astro 7.0
#29"The .astro compiler has been rewritten in Rust.". I'm personally awaiting the rewrite to assembly.
Rust is so powerful it rewrites your code to assembly on-demand every time you compile ;)
Re: Astro 7.0
#30For me currently nothing beats Astro + Claude Code for building sites, maybe with some image generator sprinkled in. Build time improvements are always welcome, great job!