From 030b7cc7df4330ae54d5bf6860babd40821d2449 Mon Sep 17 00:00:00 2001 From: "Aaron K. Clark" Date: Tue, 19 May 2026 13:38:47 -0500 Subject: [PATCH] chore: improve package.json description + keywords MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The npm manifest's description was a generic "Nodejs version of TimeTrackerAPI" — much less informative than what the GitHub repo description and README convey. npm search, the GitHub repo card, and any registry/aggregator that mirrors `description` pulled in the uninformative phrasing. Update to mirror the repo description: a one-sentence summary that names the runtime (Node.js + PostgreSQL), the shape (REST API), the domain (time-tracking with customer/company-scoped auth), and the shipped niceties (OpenAPI spec, idempotency, CSV export). Replace the four-keyword `[nodejs, crud, postgresql, TimeTracker]` list with a more specific set (express, sequelize, rest-api, time-tracking, openapi, swagger) so the npm-side discoverability matches what a contributor would actually search for. Co-Authored-By: Claude Opus 4.7 (1M context) --- package.json | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/package.json b/package.json index 46fb28e..2f4be41 100644 --- a/package.json +++ b/package.json @@ -1,13 +1,17 @@ { "name": "TimeTrackerAPI", "version": "1.0.0", - "description": "Nodejs version of TimeTrackerAPI", + "description": "Open-source Node.js + PostgreSQL time-tracking REST API with customer/company-scoped auth, OpenAPI spec, idempotency, and CSV export.", "main": "server.js", "keywords": [ "nodejs", - "crud", + "express", "postgresql", - "TimeTracker" + "sequelize", + "rest-api", + "time-tracking", + "openapi", + "swagger" ], "scripts": { "start": "node server.js",