test
elm-live
test | elm-live | |
---|---|---|
3 | 4 | |
233 | 1,049 | |
0.9% | - | |
5.4 | 0.0 | |
2 months ago | almost 2 years ago | |
Elm | JavaScript | |
BSD 3-clause "New" or "Revised" License | 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.
test
-
Setting up an Elm project in 2022
The de-facto standard for testing an Elm application is elm-test. However, as noted in the README:
-
Porting Elm to WebAssembly
Once all that handwritten C code was solid, I needed to make sure the C generated from Elm was working properly. I found the source for the core library's unit tests and decided to port them into my project and add some of my own tests. You can run the tests in WebAssembly in your browser too. (Funnily enough, one of the biggest challenges was getting the Elm Test framework itself to run! The framework is more complex than the tests themselves. I still need to come back to the fuzzer tests!)
-
Causing Bedlam in Elm
Lesson Learned: Elm has built in recursion improvements for a variety of positive reasons, and you should think in recursion to solve looping problems. Use property/fuzz tests and bounds checking with early exit to prevent this from locking up your UI (i.e if > 9000, omg abort). If you’re algorithm is reasonable, but the data set is just gigantic, offload to a server instead for more horsepower. Or Workers if you don’t have server chops, can’t upload the large data, or don’t trust your server devs. (“But Doc, I’m the server dev!” Good joke. Ever̸y̴b̸ody laugh. Roll on s̵͓̆nâ̶̱re drum. Curtains.)
elm-live
-
Getting Tailwind to Work with Elm Book
However, getting it to work in elm-live, which elm-book wraps, was a bit challenging. I wanted to layout how to get this to work in case you’d like to use Tailwind or your own CSS framework.
-
friendly tip of the day: kill-elm-reactor
I recently discovered you can also use `npx kill-port 8000` to kill any process hosting at that particular port. I use elm-live, but I think it works for any service.
-
Setting up an Elm project in 2022
First on our list is elm-live. From their README, elm-live provides:
-
React to Elm Migration Guide
Using elm-live, you’ll run elm-live and your changes + compile errors will be reflected quickly in the open browser window.
What are some alternatives?
Google Test - GoogleTest - Google Testing and Mocking Framework
vite-plugin-elm - A plugin for Vite enables you to compile an Elm application/document/element
ut - C++20 μ(micro)/Unit Testing Framework
elm-library-installer - Installs Elm libraries in corporate networks.
CppUTest - CppUTest unit testing and mocking framework for C/C++
vite-plugin-full-reload - ♻️ Automatically reload the page when files are modified
Catch - A modern, C++-native, test framework for unit-tests, TDD and BDD - using C++14, C++17 and later (C++11 support is in v2.x branch, and C++03 on the Catch1.x branch)
Preact - ⚛️ Fast 3kB React alternative with the same modern API. Components & Virtual DOM.
Google Mock
elm-css - Typed CSS in Elm.
benchmark - A microbenchmark support library
jaguar - Use live reloading over WiFI to turbo-charge developing for your ESP32.