crank
ava
crank | ava | |
---|---|---|
13 | 34 | |
2,673 | 20,623 | |
0.1% | 0.1% | |
8.1 | 8.0 | |
8 days ago | 4 days ago | |
TypeScript | JavaScript | |
MIT 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.
crank
-
Coroutines in JavaScript for Web Components
If you enjoy this approach, you might enjoy the Crank JS framework. https://crank.js.org/
> Crank uses generator functions to define stateful components. You store state in local variables, and `yield` rather than `return` to keep it around.
- Crank.js, the Just JavaScript Framework
-
A Proposal for an asynchronous Rust GUI framework
I'm very interested in seeing if using the commonly implemented forms of compiler support for async programming can also be well used for GUI programming. One wishawa[0] is also perusing this approach in Rust but I first came upon this idea from the crank-js[1] authors. It wasn't clear to me why that one never went anywhere. Was it failure with the approach or was React just a good solution in the space? I can say this though, there's something strikingly elegant about those initial samples of using JavaScript generators for components.
[0]: https://github.com/wishawa/async_ui
[1]: https://github.com/bikeshaving/crank
Take a look at crank.js, a JavaScript framework where components can be written as async functions or as generators. It seems similar to what you're trying to do :)
- UnsuckJS: Progressively enhance HTML with lightweight JavaScript libraries
-
Algebraic Effects β You Can Touch This (2019)
Well there's https://crank.js.org that uses native js generators where you would you normally put hooks in. Never used it but looked like a very neat idea.
-
What happens if you mix React, Mobx and generators*? Ok, let's do it!
Reminds me of https://github.com/bikeshaving/crank, which was rather fun for a PoC I made a while back.
-
Are my components supposed to render multiple times?
Strictly speaking, the framework hides this complexity away, but it still exists and it is the framework that's now paying the extra cost. Of course a framework is allowed, and should, when possible, hide away these things. For example Crank.js uses generators to allow for async Components as first class citizens, https://github.com/bikeshaving/crank, but they're still having to deal with the pitfalls of asynchronous work.
-
React State Museum - Examples to help portray the how, why, which, pros, and cons of various state management systems in the React ecosystem
To give the author of https://crank.js.org/ due credit, after reading through the descriptive posts I was impressed by the amount of thought and design that went into it.
-
What's New in React 18?
> What do you propose as an alternative?
There are lots of alternatives, but perhaps the simplest would have been to use async generators. This is how Crank[0] (mentioned elsewhere in this thread) works, and it allows you to do anything (AFAIK) that's possible with hooks with a much simpler and more testable API.
> So, sure, there are limitations and rules you have to pay attention to with hooks... but that's just programming.
No, it's not. The biggest problem with React hooks is that they are not composed of transferable knowledge, meaning memorizing these rules and patterns does not transfer outside of React; likewise, I can't use much of the knowledge I have already built up over many years of my career when using hooks. It's the same argument that's made against Rails, where you have to learn tons of Rails-specific idioms (on top of having to understand general concepts like relational database access patterns) instead of just writing code in a way that's more direct and intuitive for anyone.
My brain has limited RAM. The more things I have to keep in my head when developing against an API, the more likely I am to make a mistake. With every release of React, I seem to have to keep more and more of these details in my brain as I work. Contrast this with something like Svelte, where you really only need to fully grok about two concepts to use it effectively. I understand that this is the tradeoff the React team made, but I'm not convinced it's worth it.
[0]: https://crank.js.org/ and https://crank.js.org/blog/introducing-crank
ava
-
Painless CLI integration testing
We use Jest Framework for testing. Jest is not a dogma, and, of course, in its place can be any other test runner, such as Mocha or Ava. Let's focus on tests. I'll provide a short example because I donβt want to waste your time. You can find the full version here. It's crucial to read the comments in the code below. Let's go!
-
Speeding up the JavaScript ecosystem β The barrel file debacle
> In the popular jest test runner, each test file is executed in its own child process.
Is that confirmed?
I've been following this issue:
https://github.com/jestjs/jest/issues/6957
And what Jest actually does is still kind of muddy.
In contrast to that, other test runners like AVA have a clear description what happens when:
https://github.com/avajs/ava/blob/main/docs/01-writing-tests...
-
What Tools Are You Using to Test Your Code?
I've been looking at using japa or ava for web server testing but was curious what others were using and why.
-
[2023-07-14] Razuberi Development Update
Continued work on the test suite. Implementing AVA, with snapshotting. Making a lot of effort to have the snapshot directory structure match the test262 test directory structure by generating AVA test files.
-
Ask HN: What's your favorite software testing framework and why?
You might want to give ava a spin:
https://github.com/avajs/ava/
It has a TAP reporter, but more importantly, as opposed to the more popular solutions, like Jest, the way it achieves parallelism is explained in the docs and won't change anytime soon, thus preventing wonky, hard to debug errors which occur when this part is abstracted away.
-
The new React's documentation
I switched to ava for that reason and have been very happy with it. But vitest looks nice, too. Thanks for the pointer.
-
How to create and publish a TypeScript library with ease
Runs unit tests using AVA.
-
Express API Testing
Last but not least important are ava, uvu and tape; they are a really light and fast test runners.
-
Unit testing: What to use, and how?
I've had some good experiences with Ava + Sinon. I've personally disliked Jest because it seemed to do some weird trickery in the background that prevented me from using ES modules.
-
Tech stack discussion
Ava for a simpler environment than Jest, which I usually use. I need to check how to mock ESM with it, though.
What are some alternatives?
js-framework-benchmark - A comparison of the performance of a few popular javascript frameworks
jest - Delightful JavaScript Testing.
React - The library for web and native user interfaces.
ocapi-proxy - Salesforce Commerce Cloud Node.js OCAPI Proxy Router
async_ui - Lifetime-Friendly, Component-Based, Retained-Mode UI Powered by Async Rust
vitest - Next generation testing framework powered by Vite.
sucrase - Super-fast alternative to Babel for when you can target modern JS runtimes
tape - tap-producing test harness for node and browsers
solid - A declarative, efficient, and flexible JavaScript library for building user interfaces.
mocha - βοΈ simple, flexible, fun javascript test framework for node.js & the browser
vue-promise-dialogs - A tiny & modern library that allows you to work with dialogs as with asynchronous functions.
tap - Test Anything Protocol tools for node