HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
repro-dev
repro
TypeScript2023–2023
repro-dev / repro

repro

Discover this repository through its Hacker News conversations.

2Distinct people
2Mentions
0Explicit recommenders
1GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2023-04-03 16:29:56 UTC to 2023-04-04 13:48:17 UTC.

012023-04-03 16:00:00 UTC to 2023-04-03 17:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 3, 16:002023-04-03 17:00:00 UTC to 2023-04-03 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-03 18:00:00 UTC to 2023-04-03 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-03 19:00:00 UTC to 2023-04-03 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-03 20:00:00 UTC to 2023-04-03 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-03 21:00:00 UTC to 2023-04-03 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-03 22:00:00 UTC to 2023-04-03 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-03 23:00:00 UTC to 2023-04-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-04 00:00:00 UTC to 2023-04-04 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-04 01:00:00 UTC to 2023-04-04 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-04 02:00:00 UTC to 2023-04-04 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsApr 4, 02:002023-04-04 03:00:00 UTC to 2023-04-04 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-04 04:00:00 UTC to 2023-04-04 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-04 05:00:00 UTC to 2023-04-04 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-04 06:00:00 UTC to 2023-04-04 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-04 07:00:00 UTC to 2023-04-04 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-04 08:00:00 UTC to 2023-04-04 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-04 09:00:00 UTC to 2023-04-04 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-04 10:00:00 UTC to 2023-04-04 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-04 11:00:00 UTC to 2023-04-04 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-04 12:00:00 UTC to 2023-04-04 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-04 13:00:00 UTC to 2023-04-04 14:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsApr 4, 13:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Apr 3, 16:002023-04-03 16:00:00 UTC2023-04-03 17:00:00 UTC101
Apr 3, 17:002023-04-03 17:00:00 UTC2023-04-03 18:00:00 UTC000
Apr 3, 18:002023-04-03 18:00:00 UTC2023-04-03 19:00:00 UTC000
Apr 3, 19:002023-04-03 19:00:00 UTC2023-04-03 20:00:00 UTC000
Apr 3, 20:002023-04-03 20:00:00 UTC2023-04-03 21:00:00 UTC000
Apr 3, 21:002023-04-03 21:00:00 UTC2023-04-03 22:00:00 UTC000
Apr 3, 22:002023-04-03 22:00:00 UTC2023-04-03 23:00:00 UTC000
Apr 3, 23:002023-04-03 23:00:00 UTC2023-04-04 00:00:00 UTC000
Apr 4, 00:002023-04-04 00:00:00 UTC2023-04-04 01:00:00 UTC000
Apr 4, 01:002023-04-04 01:00:00 UTC2023-04-04 02:00:00 UTC000
Apr 4, 02:002023-04-04 02:00:00 UTC2023-04-04 03:00:00 UTC000
Apr 4, 03:002023-04-04 03:00:00 UTC2023-04-04 04:00:00 UTC000
Apr 4, 04:002023-04-04 04:00:00 UTC2023-04-04 05:00:00 UTC000
Apr 4, 05:002023-04-04 05:00:00 UTC2023-04-04 06:00:00 UTC000
Apr 4, 06:002023-04-04 06:00:00 UTC2023-04-04 07:00:00 UTC000
Apr 4, 07:002023-04-04 07:00:00 UTC2023-04-04 08:00:00 UTC000
Apr 4, 08:002023-04-04 08:00:00 UTC2023-04-04 09:00:00 UTC000
Apr 4, 09:002023-04-04 09:00:00 UTC2023-04-04 10:00:00 UTC000
Apr 4, 10:002023-04-04 10:00:00 UTC2023-04-04 11:00:00 UTC000
Apr 4, 11:002023-04-04 11:00:00 UTC2023-04-04 12:00:00 UTC000
Apr 4, 12:002023-04-04 12:00:00 UTC2023-04-04 13:00:00 UTC000
Apr 4, 13:002023-04-04 13:00:00 UTC2023-04-04 14:00:00 UTC110

What Hacker News says

2 sources

Show HN: A browser extension to make reproducing bugs easier

Hi HN! I've been working on this project for a while and I'd love to get your feedback. Repro is a browser extension for creating replayable bug reports. It uses session recording (like FullStory, LogRocket, rrweb, etc.) as well as capturing console logs/errors and network requests, to give a detailed bug report in a couple of clicks. Here's an example recording: https://app.repro.dev/recordings/90e5b422-a5d5-4d6d-9e6b-09e.... I've got lots of ideas for improvements, but I'd love to hear whether you'd find a tool like this useful, either here or shoot me an email at gary [at] repro [dot] dev. Thanks!
3 points · Open discussion
Foremost, thanks for choosing a business friendly license. I know that statement is going to ruffle feathers, but I'm still grateful. I'm also grateful for you choosing postgresql You will want to strongly consider pinning a node version since it's a huge list of possible values that can go there: https://github.com/reprohq/repro/blob/main/apps/api-server/D... (it certainly looks like `node:18` is the correct one based on https://github.com/reprohq/repro/blob/main/.tool-versions#L1 ) Also, please don't hard-code AWS credential configurations like this; if you're using the AWS sdk it automatically supports a wide range of credential discovery mechanisms, which certainly includes those famous env-vars, but by not hard-coding that it allows the server to work correctly in a lot more diverse configurations (EKS, IMDSv2, AWS_PROFILE, etc): htt
Read the rest
In Show HN: Repro – an open-source bug reporting and debugging tool for web apps

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.