0l1v3rr / 0l1v3rr/github-readme-tech-stack
Doesn't work for custom SVGs
- Dominant language
- TypeScript
- Stars
- 261
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
The generated URL is simply too long when you add custom SVGs. I built one with just 2 lines and it generated an URL over 40k characters long. Even tinyurl can't handle it (max 32k), browsers also say the URL is too long.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to '[...](https://github-readme-tech-stack.vercel.app/)'
2. Go to 'do your stuff and go to step 6/7 '
3. Add 'about 11 svgs about ~3KiB across two lines'
4. Generate a _Titanoboa_ type of URL
**Expected behavior**
It should generate a 'way shorter URL' capable of being read. Or at least, it should generate a PNG image that you could download and add it to a shorter link.
Contributor guide
Research direction
The issue is about URL length when custom SVGs are added. Look at the URL generation logic, likely in the API routes or utility functions that serialize SVG data. Check how SVGs are encoded and if compression or alternative output formats (like PNG) are supported. The goal is to shorten the URL or provide a downloadable image.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, react, tailwindcss, typescript
- Domain
- frontend, tooling, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100