Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Testing: unit tests for SVG path length measuring

Closed Beginner friendly
#182 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
testing

Research direction

Start with pathLength and shapeLength in lib/svg/inspect.ts, then check lib/logo/animate.ts to see how the returned lengths are used. Add Vitest cases for a line, rectangle, circle, cubic and arc against known lengths within 1%, plus a check that relative and absolute path commands return the same value. Done means those tests pass under pnpm test.

Written by the indexing model from the issue text.

Description

difficulty: easy good first issue testing

Summary

Add Vitest tests for pathLength and shapeLength in lib/svg/inspect.ts, used by the animated logo export.

Where to look

  • lib/svg/inspect.ts
  • lib/logo/animate.ts: how the lengths are used

Acceptance criteria

  • Tests cover a line, a rectangle, a circle, a cubic and an arc against known lengths (within 1%).
  • Relative and absolute commands give the same result.
  • pnpm test passes.

Getting started: fork the repo, then pnpm install and pnpm dev (Node 22+, pnpm 11, no API keys). Before opening a PR, run pnpm typecheck && pnpm test && pnpm lint && pnpm format:check && pnpm check:dashes && pnpm build. See CONTRIBUTING.md and the first contribution walkthrough.

Everything needed is in the repository. This doesn't need maintainer access, secrets or paid services. Comment below to claim it, and ask questions here any time.

Dominant language
TypeScript
Stars
11
Forks
3
Avg merge
5h 58m
Merged PRs (30d)
35

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from yakew7/DesignHub

All issues in yakew7/DesignHub

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.