How Vue 3 and pdf-lib Enable Browser-Based PDF Splitting by File Size

·1 views

A developer tutorial on DEV Community outlines how to build a browser-based PDF splitter that divides files by target size using Vue 3 and the pdf-lib library. Unlike splitting by page count, size-based splitting is complex because PDF file size varies widely depending on image resolution, font embedding, and content type. The proposed approach uses greedy page accumulation, incrementally saving the PDF after each page addition to estimate byte size rather than relying on simple arithmetic. When a page would push the current chunk over the size limit, the tool closes that file and begins a new one, ensuring no pages are lost even if a single page exceeds the target. The finished tool packages all output chunks into a ZIP file and includes user-selectable compression levels and a progress indicator for handling large documents.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

10 Open-Source Tools That Can Replace Costly SaaS Subscriptions

A roundup published on DEV Community highlights ten open-source GitHub repositories designed to replace expensive paid software services costing hundreds of dollars monthly. The list covers a wide range of use cases, including cloud deployment, AI coding agents, web scraping, PDF editing, and self-hosted AI chat interfaces. Notable entries include Coolify as a Heroku alternative, Open WebUI replacing ChatGPT Plus, Supabase standing in for Firebase, and Stirling PDF offsetting Adobe Acrobat Pro costs. Several tools have amassed tens of thousands of GitHub stars, indicating strong community adoption and active development. All featured projects are self-hostable, meaning users can run them on their own infrastructure to avoid recurring subscription fees.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer builds Clash Royale stats site that hides win rates with under 30 samples

A developer behind Royale Cards, a Clash Royale guide site, has shared lessons from building a small static site hosted on Cloudflare Pages that prioritizes data transparency. The site enforces a strict rule: win rates are only displayed when at least 30 battle samples exist, with a 'sample too small' note shown otherwise. Each of the roughly 133 card pages covers stats across all 14 levels, arena unlock info, and top deck combinations, keeping pages focused for both search engines and mobile users. For the current K.H.A.O.S season, the site clearly separates officially confirmed facts from editorial analysis, helping readers distinguish between the two. The developer's key takeaway is that being upfront about data limitations is a genuine differentiator for niche stats sites.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

SaijinOS Builds Web Reader That Treats Page Content as Data, Not Commands

By day 578 of development, SaijinOS implemented a tightly scoped public web reader capable of fetching a single allowlisted page while strictly separating retrieved content from system instructions. The core design principle holds that text found on a web page — including any embedded prompt-injection attempts — is treated as content only, never as executable commands. The reader's authority is deliberately narrow: it performs a bounded fetch and returns a structured result, with no permissions to write files, update memory, call models, or summarize output. Each redirect in a request chain is individually revalidated, so initial approval of a URL does not grant permission to follow it to an unrelated domain. The architecture also distinguishes between 'found a link' and 'learned this,' preventing unreviewed expansion of trusted sources or automatic ingestion of candidate pages.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

PyOhio Speaker Reflects on Oracle Joke After Attendee Files Code of Conduct Complaint

A developer delivering the closing keynote at PyOhio included a recurring joke dismissing Oracle as a poor technical choice, drawing laughs from the audience. After the talk, an attendee who had built their career around Oracle expertise filed a discomfort report through the conference's Code of Conduct grievance process. The attendee told organizers they felt unexpectedly singled out and uncertain about discussing their work with other conference-goers. The speaker acknowledged that, unlike other technologies mentioned in the talk, Oracle was never given a redemptive framing, effectively leaving its practitioners as the unintended butt of the joke. Reflecting on the feedback, the speaker concluded that dismissing the complaint as oversensitivity would be both defensive and condescending, and committed to reconsidering the bit for future talks.

0 comments Read more at DEV Community