uvu
typescript-eslint
uvu | typescript-eslint | |
---|---|---|
21 | 123 | |
2,938 | 14,590 | |
- | 0.8% | |
3.0 | 9.9 | |
26 days ago | 5 days ago | |
JavaScript | TypeScript | |
MIT License | GNU General Public License v3.0 or later |
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.
uvu
-
Express API Testing
Last but not least important are ava, uvu and tape; they are a really light and fast test runners.
-
Test Svelte Component Using Vitest & Playwright
Vitest: A Vite-native unit test framework. (alternative: Jest, uvu)
-
SvelteKit uvu Testing: Fast Component Unit Tests
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.
-
Creating a Chai like assertion library using proxies
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).
-
Test Coverage in Svelte
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
-
Don't be a dolt like me: Set Up Debugging in VSCode!
Yes! There’s even an example test written for the svelte counter demo in the repo’s examples!
- Recommendations for a lightweight, idiomatic testing framework? (looking for a diamond in the rough, not the top 5 most popular)
-
From Jest to Vitest - Migration and Benchmark
uvu is what I’d recommend.
-
Chaijs.com just let their domain expire
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.
-
Why Jest is not for me
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).
typescript-eslint
-
Mastering Type-Safe JSON Serialization in TypeScript
Typescript-eslint can assist in this task. This tool helps identify all instances of unsafe any usage. Specifically, all usages of JSON.parse can be found and it can be ensured that the received data's format is checked. More about getting rid of the any type in a codebase can be read in the article Making TypeScript Truly "Strongly Typed".
-
Oxlint – written in Rust – 50-100 Times Faster than ESLint
> Only lint files that have changed? How hard that is?
Quite hard, especially since type-aware rules from e.g. https://typescript-eslint.io/ mean that changing the type of a variable in file A can break your code in file B, even if file B hasn't changed.
-
How to Do a TypeScript Conversion: an opinionated take on gradual conversions
The article only touches this: when converting to TypeScript, `any` is useful, but in the end you don't want this type in your codebase - so don't forget to use typescript-eslint [0] and turn on those no-unsafe-* rules which guard against `any` leaking into your code.
[0] https://github.com/typescript-eslint/typescript-eslint
- How do I add additional rules to my typescript-eslint settings?
- What's the best config for typescript-eslint?
- How do you add angular-eslint to your typescript-eslint config?
- What's the best typescript-eslint config?
-
The Best ESLint Rules for React Projects
By convention, React components should be named in PascalCase. @typescript-eslint has the config we need, and though we can't specifically target React components, we can target variables (and set some other conventions while we're at it):
- Open source public fund experiment - One and a half years update
- Never touch those //ts-ignores
What are some alternatives?
jest - Delightful JavaScript Testing.
eslint-config-google - ESLint shareable config for the Google JavaScript style guide
AVA
angular-eslint - :sparkles: Monorepo for all the tooling related to using ESLint with Angular
svelte-starter-kit - Svelte with brilliant bells and useful whistles
ts-standard - Typescript style guide, linter, and formatter using StandardJS
ava - Node.js test runner that lets you develop with confidence 🚀
zod - TypeScript-first schema validation with static type inference
Sinon.JS - Test spies, stubs and mocks for JavaScript.
node-clinic - Clinic.js diagnoses your Node.js performance issues
supertest - 🕷 Super-agent driven library for testing node.js HTTP servers using a fluent API. Maintained for @forwardemail, @ladjs, @spamscanner, @breejs, @cabinjs, and @lassjs.
ts-node - TypeScript execution and REPL for node.js