askama
Ink
askama | Ink | |
---|---|---|
28 | 64 | |
3,111 | 25,811 | |
- | - | |
9.3 | 6.2 | |
1 day ago | 19 days ago | |
Rust | TypeScript | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
askama
-
Deploying your Rust WASM Game to Web with Shuttle & Axum
I have inlined the CSS here, and you can use Rust-based tooling like Lightning CSS to minify and bundle CSS here. You might also want to create a Rust build script to generate the HTML from a template, using the askama crate (works a little like Jinja).
-
Getting Started with Actix Web - The Battle-tested Rust Framework
This adds askama itself as well as the Responder trait implementation for the askama::Template type. askama expects your files to be in a subfolder of the project root called templates by default, so let's create the folder and then create an index.html file with the following HTML code in:
-
Getting Started with Axum - Rust's Most Popular Framework
You can also use HTML templating with crates like askama, tera and maud! This can be combined with the power of lightweight JavaScript libraries like htmx to speed up time to production. You can read more about this on our other article about using HTMX with Rust which you can find here.. We also collaborated with Stefan Baumgartner on an article for serving HTML with Askama!
-
RustGPT: ChatGPT UI Built with Rust, Htmx, SQLite
This is such a great project, thank you for sharing! It seems like you're getting the usual dump of negativity around HTMX... but as usual, not much coming from anyone who's actually tried to build something small/medium-sized. I keep hearing that this stack "would" fall apart in a bigger project, but I never hear any concrete, empirical descriptions of issues that actually do arise.
I'll offer one here... using HTMX usually means you're going to be writing HTML templates, and HTML templating languages don't have much IDE support. I really miss goto-definition etc. when I'm writing Jinja templates.
That being said, I've personally found Rust/HTMX to be a magnificent combo. I personally find writing backend endpoints in Rust to be no more cumbersome than any other language (after becoming comfortable with Rust)... and there's massive gains from the incredible tooling and type system.
I wonder if you've considered using Askama for your templates? It has a Axum integration that cleans up some of the boilerplate around template rendering. There's also an open PR for block fragments [1], which will make componentization of HTML fragments much easier, as discussed in this essay on the HTMX site [2].
We need more projects like this to demonstrate how useful, highly-interactive apps are made with HTMX. I'd encourage skeptics to try the same before writing it off.
[1] https://github.com/djc/askama/pull/824
-
Announcing Stilts v0.1 A new template engine like Askama
This templating languge / engine is heavily inspired by Askama, but brings more rust into your template code. The project is still in early stages and is likely filled with bugs but I wanted to get something out there to get some feedback on.
-
Full-Stack-Rust: Which approach in Frontend?
Askama
-
Becoming Rustacean:Awesome Free Online Resources to Learn Rust Programming
Rust allows me to mainly only run the application to confirm things work from a business perspective.
For people starting out building stuff in rust - understand that there is a distinction of async code and libraries and can lead to confusing compiler errors if you don't realize there is a distinction. It's simple in hindsight but did cause me to waste hours barking up the wrong trees at first. Other wise just learn about `match` and Result/Option types asap, they're fundamental.
https://github.com/http-rs/tide tide is great to create an http server / routes
https://github.com/djc/askama I use this to template out HTML and it checks all my boxes, dynamic data, passing in functions, control flow.
https://github.com/launchbadge/sqlx sql interface for a variety of backend, async safe.
https://github.com/seanmonstar/reqwest http client to make requests
Rust is amazing, don't let the initial few speed bumps discourage you - building real things with rust is no more challenging today than any other modern language stack.
-
Axum Railway Template, looking for peer review
I also Suggest using https://crates.io/crates/askama for Templates. even though it can be hard to get use to and they are compile time only It allows you to use Rust functions directly within the Template code. Which can make your life easier.
-
Askama's markdown feature won't let me enable it
It was a bug in askama that was fixed. The solution is to use a newer version that contains the fix, but they have not released a new version of askama since fixing the bug, so 0.11.1 still contains the bug. It seems like 0.12 has been a long time coming but should finally be coming soon: https://github.com/djc/askama/issues/722
-
Rust for Web Development | An Honest Evaluation
A good example is Askama, which should look good to folk from the python / django / jinja world: https://github.com/djc/askama
Ink
-
I created a simple CLI tool that helps you code FAST!
I've always wanted to build a CLI tool, and when I realized that you can build one using React with Ink, I converted my Python script into a CLI tool.
-
Delete git branches in batches
⚠️ Git for Windows Terminal is currently not supported, and the tool is limited to ink. We will look for alternatives later. Please use CMD, Vscode terminal's Git... terminal
-
Setup Simple Web UI for Node.js App in Seconds
There is a good solution for some of those cases - ink. With ink, I can implement text-based UI with knowledge of React, which is neat but there are still some caveats for my usages:
-
Building Reactive CLIs with Ink - React CLI library
Looks cool, right? Building a similar UI in the terminal without any library would be quite hard, though, thanks to Ink it's almost as easy as building any frontend UI with React.
-
Terminal-like output library for js?
ink?
-
Synchronous File Reading and Writing in Node.js
I'm writing a CLI with ink. Writing async code is important as to not block the rendering and respond to user input. I have a few loading animations that update every 100ms. Synchronous operations can make the animation hang for >500ms, making the animation choppy.
-
Launch HN: Resend (YC W23) – Email API for Developers Using React
You get the comfort of using react components instead of fighting with HTML tables to make your emails look nice. I think it's awesome! It's analog to what ink[0] does with CLI outputs. Sure, you could write fancy CLI outputs in bash, but ink takes the pain out of it and makes it easy.
[0] https://github.com/vadimdemedes/ink
-
Is Node.js a good way to implement a CLI app with persistence?
Due to Node's asynchronous behavior, it makes Node great for long-running processes that make a lot of HTTP requests, database calls, and other async ops, like a web server or a REST API. However, if I am making a CLI tool for pretty much personal use only, with very minimal async operations, then blocking the event loop with a synchronous function that will resolve almost immediately will make no difference perceivable to a human brain or have any speed benefits that someone can actually observe (think `fs.readFileSync` or `require('dotenv') of 10 line config file, or a quick embedded db (sqlite) query with only ~100 records. I'm wondering what the best way to implement the database part of the app synchronous. I can read/write to JSON files but it would be tricky because the data is relational, and some complex joins and other data wrangling operations are required (complex to perform in JS but are easy to implement in a SQL statement). It's not important what the operations are, that's not the point of this post. This is mostly a personal project of interest: making this CLI tool completely avoiding any async operations/using no promises. I would like to use node tho, as I said this is just out of interest and I also want to experiment with several CLI libraries such as Ink or Cliffy.
- Ink: React for interactive command-line apps
- Make interactive command-line apps with React
What are some alternatives?
tera - A template engine for Rust based on Jinja2/Django
Commander.js - node.js command-line interfaces made easy
maud - :pencil: Compile-time HTML templates for Rust
oclif - CLI for generating, building, and releasing oclif CLIs. Built by Salesforce.
minijinja - MiniJinja is a powerful but minimal dependency template engine for Rust compatible with Jinja/Jinja2
blessed - A high-level terminal interface library for node.js.
handlebars-rust - Rust templating with Handlebars
nestjs-commander - A module for using NestJS to build up CLI applications
sailfish - Simple, small, and extremely fast template engine for Rust
tui-rs - Build terminal user interfaces and dashboards using Rust
markup.rs - A blazing fast, type-safe template engine for Rust.
PyLaTeX - A Python library for creating LaTeX files