Sample Code for Test - useCommonUtil.ts export default () => { const isItemInListByType = <T>( list: T[] | undefined, key: keyof T, value: T ): boolean => { if (!list || list.length === 0) { console.error("List is empty or undefined."); return false; } const itemIndex = list.findIndex((item) => item[key] === value[key]); if (itemIndex === -1) { console.error(`Item with ${String(key)}=${value} not found in the list.`); return false; } return true; }; return { isItemInListByType, };}; Here is a step to add unit test in Nuxt Project
Configure Vitest - Create a vitest.config.ts file in the root of your project
import { defineConfig } from 'vitest/config';export default defineConfig({ test: { globals: true, environment: 'jsdom', setupFiles: './vitest.setup.ts', // Optional: Add setup file for global configurations },});
If you need to configure global settings (e.g., mocking or extending Jest matchers), create a vitest.setup.ts file
import '@testing-library/jest-dom';
Create a Test File
create a test on the same level as useCommonUtil.ts > useCommonUtil.test.ts import useCommonUtil from './useCommonUtil';import { describe, it, expect } from 'vitest'describe('useCommonUtil', () => { const { isItemInListByType } = useCommonUtil(); const sampleList = [ { id: 1, name: 'Item 1' }, { id: 2, name: 'Item 2' }, { id: 3, name: 'Item 3' }, ]; it("should return true if the item exists in the list by key", () => { const result = isItemInListByType(sampleList, "id", { id: 2, name: "Item 2" }); expect(result).toBe(true); }); it("should return false if the item does not exist in the list by key", () => { const result = isItemInListByType(sampleList, "id", { id: 4, name: "Item 4" }); expect(result).toBe(false); }); it("should return false if the list is empty", () => { const result = isItemInListByType([], "id", { id: 1, name: "Item 1" }); expect(result).toBe(false); }); it("should return false if the list is undefined", () => { const result = isItemInListByType(undefined, "id", { id: 1, name: "Item 1" }); expect(result).toBe(false); }); it("should return false if the key does not match any item in the list", () => { const result = isItemInListByType(sampleList, "name", { id: 1, name: "Nonexistent Item" }); expect(result).toBe(false); }); it("should handle objects with additional properties gracefully", () => { const extendedList = [ { id: 1, name: "Item 1", extra: "Extra 1" }, { id: 2, name: "Item 2", extra: "Extra 2" }, ]; const result = isItemInListByType(extendedList, "id", { id: 1, name: "Item 1", extra: "Extra 1" }); expect(result).toBe(true); });});
Run Tests
bun test Sample Run Result bun test v1.2.2 (c1708ea6)composables\useCommonUtil.test.ts:✓ useCommonUtil > should return true if the item exists in the list by keyItem with id=[object Object] not found in the list.✓ useCommonUtil > should return false if the item does not exist in the list by keyList is empty or undefined.✓ useCommonUtil > should return false if the list is emptyList is empty or undefined.✓ useCommonUtil > should return false if the list is undefinedItem with name=[object Object] not found in the list.✓ useCommonUtil > should return false if the key does not match any item in the list✓ useCommonUtil > should handle objects with additional properties gracefully 6 pass 0 fail 6 expect() callsRan 6 tests across 1 files.
I tried contributing to #KartaView for the first time on my ebike - it's like the Google Street View but anyone can contribute kinda like #Mapillary amd the account is same as your account in #osm
Fedora Considers Reducing The Scope That BIOS Systems Can Hold Up A Release
Given that non-UEFI BIOS systems are quite old at this point and Intel/AMD systems for the past number of years have all supported UEFI, another change proposal being considered this week by Fedoa Linux is limiting the release-blocking status of various (non-UEFI) BIOS systems... phoronix.com/news/Fedora-Non-U…
Given that non-UEFI BIOS systems are quite old at this point and Intel/AMD systems for the past number of years have all supported UEFI, another change proposal being considered this week by Fedoa Linux is limiting the release-blocking status of vari…
not sure I like that direction, there are plenty of cases or modern systems that only support EFI, e.g. install Linux on a MacPro T2 with Intel chip. Runs only with EFI boot (Ubuntu installed in my case)
In addition to Blender 5.0 supporting HDR on Linux when using the Vulkan API and with Wayland, another important high dynamic range (HDR) milestone landed this week into Blender: the ability to both import and export HDR videos.
Ayn Gaming Handhelds To See Better Linux Support With New Open-Source Driver
Ayn is a Chinese brand of handheld gaming devices that have included Arm-based devices shipping Android as well as AMD Ryzen powered handhelds with Windows 11 or even the option of installing Ubuntu. Better support for the Ayn x86 gaming handheld devices is on the way with patches posted for a new Ayn platform driver for the Linux kernel... phoronix.com/news/Ayn-Handheld…
Red Hat Has Been Rewriting Bash-Based Greenboot In Rust
Greenboot is a generic health check framework for systemd on RPM-OSTree based Linux distributions. Red Hat engineers have worked on Greenboot as part of the likes of Fedora IoT and their other RPM-OSTree initiatives for checking on the overall system health with ease... phoronix.com/news/Greenboot-Ba…
Google's Gemini CLI is an open source tool that lets you access Gemini directly from your terminal, and use it to read, edit and create files locally. I walk through how to install it on Ubuntu - assuming you want to! omgubuntu.co.uk/2025/07/how-to…
A simple guide to installing and using Google's Gemini CLI on Ubuntu, a free, open source command line way to access Gemini LLM and use it to work with local files.
Any tool can be misused, my friend. This is simply a "how to" for those who /want/ to use it. It's not an opinion piece on why people /should/ use it. I don't make reader's choices for them.
Heck, this and every other AI-related tool I cover is peppered with caution about the pitfalls and perils of trusting or over-relying on AI (one comment left under this article is that I should've written it without the snark 🙃 but caution is the other side of the knowledge coin).
I'm sure your readers might find this interesting: “In one case, Google's Gemini CLI destroyed user files while attempting to reorganize them.” arstechnica.com/information-te…
I found a technician who'd work on a Linux machine, and she solved my problem (I had no wifi whatsoever) the same day that she received it.
I realize the culture of Linux "fix it yourself!" and I tried. I got a buddy to help. We couldn't figure it out, so I paid a professional to fix it and then tell me how she did it.
I want to normalize this. For Linux to be viable, it can't just be a hobby OS. Paying pros to fix it, and set it up for you, is part of that.
Free Soft&Hardware Enthusiast
in reply to Phoronix • • •