TypeScript-Website VS uvu

For new components, it does make sense to follow the style defined in the React documentation by writing components using a function definition. However, arrow functions using React.FC also remain a popular choice and are used by Vercel and the official TypeScript website

I opened a pull request to remove that, because you're right, there's no way somebody can read the whole handbook in 30 minutes!

Yep, this is my answer too - I use this pattern pretty often. For example, here's the main object that represents the TypeScript Playground at runtime: https://github.com/microsoft/TypeScript-website/blob/86901a0520855050b16b0c23bd6923212fdd0c9c/packages/playground/src/index.ts#L622-L623

In this series of articles, I intend to provide a detailed, accurate, and step-by-step explanation of how to implement a RESTful web interface using a stack of Typescript, Node.js, Dynamoose, DynamoDB, Jest, Serverless Framework, AWS, and Amazon Cognito.

Install TypeScript package: npm i -D typescript

Beyond testing your code, it's an excellent idea to write your library in TypeScript. Type errors are among the most common type of mistake in JavaScript, so using TypeScript will almost always reduce development time and may occasionally prevent you from publishing broken code if you forget to add a test. Moreover, the excellent TypeScript compiler will allow you to avoid using a bundler when publishing your package (we'll get into this more later) and will make supporting TypeScript and JavaScript users simultaneously much easier.

TypeScript is a JavaScript superset with optional type annotations checked during transpilation.

Last but not least important are ava, uvu and tape; they are a really light and fast test runners.

Vitest: A Vite-native unit test framework. (alternative: Jest, uvu)

Most important here is not to forget to include test.run() at the end… I’ve done that a few times 😅. Notice how we are able to use aliases in lines 1–3. You can see the full range of assert methods available in the uvu docs.

For the past few weeks I’ve taken the (arguably pointless) work of migrating Felte from using Jest to uvu. This is a really tedious work by itself, but one of details that would have made this work even more tedious is that Jest prefers assertions to the style of expect(…).toBe* while uvu gives you freedom to choose any assertion library, although there’s an official uvu/assert module that comes with assertions to the style of assert.is(value, expected).

Hello everyone, I'm using uvu for testing. And installed c8 for coverage. Yet it doesn't seem to be able to pick up test .svelte files. Does anyone knows how to achieve this or any other way of getting .svelte files coverage? Thanks

Yes! There’s even an example test written for the svelte counter demo in the repo’s examples!

uvu is what I’d recommend.

I really enjoy Ava [1] or anything assert-tape-like [2]. "uvu" [3] is getting a lot of love lately, but it's very feature limited and much of it's touted advantages are at the detriment to feature set.

[1] https://github.com/avajs/ava

[2] https://github.com/substack/tape

[3] https://github.com/lukeed/uvu

Jest is great for front-end (or full stack integration) testing, but I feel it's specialized for that use-case and doesn't always play nice with backend/middle-tier testing needs.

For Node, I lean towards UVU by @lukeed due to its simplicity. Its lightweight, fast, supports ESM out of the box. It feels like an easier to setup modern Mocha (without the wide array of plugins).