HarperFast/harper

Update TLS privateKey to use relative path and update tests

Closed

#307 opened on Mar 31, 2026

View on GitHubContributor guide
 (0 comments) (0 reactions) (1 assignee)JavaScript (11 forks)github user discovery
good first issue

Repository metrics

Stars
 (85 stars)
PR merge metrics
 (Avg merge 6d 4h) (222 merged PRs in 30d)

Description

https://github.com/HarperFast/harper/pull/274/changes/3382ccd9bf07f65948967ebb716c5241fd689a2c correctly updates the path for tls.privateKey to use a relative path, but this breaks the mqtt unit tests that apparently are not expecting that. We need to update the unit tests to keep passing with this change.

Contributor guide

Research direction
Update the MQTT unit tests to expect the relative path for tls.privateKey instead of absolute path.
Tech stack
javascriptnodejs
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65