shelf VS dart-sass

To be honest, there's not much to it! It's a single-file add-on for the shelf package with about 100 lines of code, and the comment for the ProxyHandler class at the top sums up the shelf-proxy package pretty well:

These are the best backend frameworks for Dart right now but you can use the shelf package if you want a slightly different approach

In this blog, I will talk about the benchmarks of Flask (Python), Express (JavaScript), Shelf (Dart), dart_frog (Dart) and Conduit (Dart), and my opinions on Dart on the server side.

There was a time, I want to start a new project and have to choose what technologies to use for the frontend and backend parts as well. Research gets me to Aqueduct and Shelf, both of them weren't looking actively developing and supported and that leads me to the idea to make my own small micro-framework like Echo for Golang or Bottle for Python. And it was easy to decide: I've had time and motivation :)

Dart Frog 🐸 es un framework web construido sobre Shelf inspirado por Next.JS, Remix y Express.

We are't using one of the frameworks for Dart on the backend (Conduit, Dart Frog) and instead built on top of shelf for both the projects we've used Dart on the backend for - one we went for a gRPC approach and the implemented a REST API.

We also need a software service that we already built in the videos mentioned above. The service we want to deploy will use the shelf server from Dart hat we already run locally and make our first requests. But this will also work if you use a aqueduct server or a conduit server.

The shelf package has always looked very well-written to me. I like the way functions and function typedefs are preferred over classes, how it uses short and simple source files, and usages of streams for requests and responses. This package makes good use of language and SDK features that only work in Dart.

| console-simple | A simple console application (basic template). | | ---------------- | -------------------------------------------------- ----- | | console-full | Console application with tests. | | package-simple | A starting point for Dart libraries or apps. | | server-shelf | Server based on shelf. | | web-simple | Web application with core libraries. |

PS: You can use normal sass package today instead of node-sass.

The main sass implementation is in dart https://github.com/sass/dart-sass, which I think is dumb because it's a fair amount slower than the old libsass written in C.

The reason they spouted was due to "Low developer resources" due to the difficulty of C, so they swapped to a language pretty much only used by Googlers. Google now has control of sass, which then gives them greater influence (even greater than just having browser majority) over CSS Spec choices (see CSS Nesting spec).

I want to be able to use the "sass" command to recompile GTK themes. The sass website links to the following github, which seems to provide the command: https://github.com/sass/dart-sass/releases/tag/1.52.3. I tried the following:

wget https://github.com/sass/dart-sass/releases/download/1.52.3/dart-sass-1.52.3-linux-x64.tar.gz

dart-sass

The first project that comes to mind is Sass, a very popular CSS preprocessor, https://github.com/sass/dart-sass

before_install: - rvm install 'ruby-3.0.0' - curl -L https://github.com/sass/dart-sass/releases/download/1.49.10/dart-sass-1.49.10-linux-x64.tar.gz > dart-sass-1.49.10-linux-x64.tar.gz - tar -xvf dart-sass-1.49.10-linux-x64.tar.gz - echo 'export PATH="$PATH:$HOME/build/amco/contentinator/dart-sass:$PATH"' >> ~/.bashrc

The tutorial below walks you through setting up unit testing for a random Sass project. If you have another project you would like to add this to, then it may require some modification to the steps to fit your needs. We will be using Dart Sass as our transpiler of choice and the Sass True framework backed by Jest to write and perform our tests.