[Feature Proposal] Better-optimized SVG encoding than URL-encoding and base64
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17k
- Forks
- 3.4k
- Avg merge
- 7h 42m
- Merged PRs (30d)
- 26
Description
I just came across this article which is relevant to Less w/ data-uri encoding: https://codepen.io/tigt/post/optimizing-svgs-in-data-uris
Basically, there was a discussion in the past about base64 vs. URL encoding for SVGs. (See: #2250 and #2184) There are a few additional optimizations in URL encoding that can make the encoding even smaller, as discovered by the research on that article. This is an improvement since URL-encoding by itself can inflate the output greater than base64 encoding.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the linked SVG data-URI optimization article and the prior discussions in #2250 and #2184 first. Then locate Less's data-uri encoding path and determine how SVG output is currently URL-encoded or base64-encoded. Done means implementing and validating a smaller SVG encoding strategy than the existing alternatives.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100