From 15f382e3c50d42e427e280a5473fe244e3b62e23 Mon Sep 17 00:00:00 2001 From: anurag629 Date: Thu, 15 Oct 2026 21:33:58 +0530 Subject: [PATCH] docs: tests can use the @/ alias now --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 416cc8f..5dbd3ad 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -103,7 +103,7 @@ npm run lint && npm run test && npm run build - Write 3 or 4 FAQs. Keep `metaTitle` under 60 characters and `metaDescription` around 150 to 160. - Keep `features` and `ogDescription` to plain Latin text; the social card font has no arrows or symbols. 2. Create `app/(tools)//page.tsx`, a `Client.tsx` client component, and `opengraph-image.tsx`. Copying `page.tsx` and `opengraph-image.tsx` from `app/(tools)/base64/` and changing the slug is the easiest start. -3. Put pure logic in `lib/.ts` with tests in `lib/__tests__/.test.ts`. Use relative imports in tests; vitest has no `@/` alias. +3. Put pure logic in `lib/.ts` with tests in `lib/__tests__/.test.ts`. Tests can import with `@/` like the app does. 4. Add the tool to the "Which tool?" dropdown in `.github/ISSUE_TEMPLATE/bug_report.yml`. The home page, metadata, JSON-LD, sitemap, manifest and command palette pick the new tool up from the registry automatically. Several people may be adding tools at the same time, so rebase on `develop` before asking for review.