HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Vinlic
WebVideoCreator
JavaScript2026–2026
Vinlic / WebVideoCreator

WebVideoCreator

🌈 A framework for rendering web animations into videos. It's implemented based on Node.js + Puppeteer + Chrome + FFmpeg, utilizing the latest browser APIs.

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

What to know before exploring

What it is

🌈 A framework for rendering web animations into videos. It's implemented based on Node.js + Puppeteer + Chrome + FFmpeg, utilizing the latest browser APIs.

GitHub

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, 5:04:57 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: 2026-03-03 09:55:57 UTC to 2026-03-03 10:29:11 UTC.

012026-03-03 09:00:00 UTC to 2026-03-03 10:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 3, 09:002026-03-03 10:00:00 UTC to 2026-03-03 11:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 3, 10: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
Mar 3, 09:002026-03-03 09:00:00 UTC2026-03-03 10:00:00 UTC101
Mar 3, 10:002026-03-03 10:00:00 UTC2026-03-03 11:00:00 UTC101

What Hacker News says

2 sources
This post smells of LLM throughout. Not just the structure (many headings, bullet lists), but the phrasing as well. A few obvious examples: - no special framework. No library buy-in. Just a URL - Advance clock. Fire callbacks. Capture. Repeat. Every frame is deterministic, every time. - We render dozens of frames that nobody will ever see, just to keep Chrome's compositor from going stale. - The fundamental insight that you could monkey-patch browser time APIs ... is genuinely clever - Where we diverged The whole post is like this, but these examples stand out immediately. We haven't quite collectively put a name on this style of writing yet, but anyone who uses these tools daily knows how to spot it immediately. I'm okay with using LLMs as editors and even drafters, but it's a sign of laziness and carelessness when your entire post feels
Read the rest
written by an LLM and the voice isn't your own. It feels inauthentic and companies like replit should consider the impact on their brand before just letting people write these kind of phoned-in blog posts. Especially after the catastrophe that was the Cloudflare Matrix incident (which they later "edited" and never owned up to). And the lede is buried at the very end: This is just a vibe-coded modification of https://github.com/Vinlic/WebVideoCreator, and instead of making their changes open source since they're "standing on the shoulders of giants", the modifications are now proprietary. In the end, being an AI company is no excuse for bad writing.
In We Built a Video Rendering Engine by Lying to the Browser About What Time It Is

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.