DEV Community: Arun Mallikarjuna

I replaced JasperReports with JavaScript – and it's 4 faster

Arun Mallikarjuna — Sun, 11 Oct 2026 10:52:37 +0000

If you build business software, you've probably met report engines: JasperReports, SSRS, Crystal Reports. They're powerful, but they need a JVM or .NET, often a paid server, and they don't fit a JavaScript stack.

The JavaScript options weren't great either. You could print HTML through headless Chrome (slow, heavy, falls over on big reports), or hand-code layouts with a document builder like pdfmake.

So I built ReportWright: an open-source (MIT) report engine for JavaScript.

What it does

You describe a report in JSON (page bands, groups, tables, charts, expressions), give it data, and it renders:

PDF (including PDF/A for archiving and PDF/UA for accessibility)
Excel, Word and PowerPoint
interactive HTML, where groups expand and drill down inside the file

It runs in Node.js or the browser. There's a drag-and-drop designer, a viewer for React, Vue, Svelte and Angular, and a CLI.

A report in a few lines

npm i @reportwright/engine@next @reportwright/fonts@next

import fs from 'node:fs';
import { render, exportPdf, defaultFontStore } from '@reportwright/engine';

const report = {
  $schema: 'reportwright/report@1',
  name: 'Orders',
  page: { size: 'A4', margins: [36, 36, 36, 36] },
  dataSources: [{ name: 'src', type: 'json', data: { rows: [
    { customer: 'Acme', amount: 1200 },
    { customer: 'Globex', amount: 850 },
  ] } }],
  dataSets: [{ name: 'Orders', source: 'src', path: '$.rows' }],
  sections: { body: { items: [{
    type: 'table', dataSet: 'Orders', x: 0, y: 0, w: 523, h: 40,
    columns: [{ width: 360 }, { width: 163 }],
    header: [{ height: 18, cells: [{ value: 'Customer' }, { value: 'Amount' }] }],
    detail: [{ height: 16, cells: [{ value: '=Fields.customer' }, { value: '=Fields.amount', style: { format: 'N2' } }] }],
  }] } },
};

const fonts = defaultFontStore();
const model = await render(report, { fontStore: fonts });
fs.writeFileSync('orders.pdf', await exportPdf(model, { fonts }));

Moving from SSRS or JasperReports

npx @reportwright/cli@next import ./my-reports --out ./imported

It converts .rdl, .rdlc, .jrxml, BIRT and ActiveReports definitions, and writes a report of what carried over and what needs a manual fix.

How fast is it?

I benchmarked it on GitHub Actions (4 vCPU) against other engines, checking every output file.

Grouped report	ReportWright	JasperReports	QuestPDF (.NET)
10,000 rows	0.91 s	3.9 s	2.7 s
100,000 rows	6.6 s	11.8 s	24.1 s
1,000 separate reports	8 s	33 s	26 s

A million rows streams in 53 s with flat memory. Against Python, the PDF library writes a million rows in 29 s versus ReportLab's 215 s.

Where it loses

I'd rather you hear it from me:

QuestPDF is about 2× faster on single invoices.
Go and Rust PDF writers are faster on tiny files, mostly because Node takes ~30 ms to start.
C tools like MuPDF and qpdf win quick edits such as merge and encrypt.

All results, wins and losses: https://github.com/MrArun005/reportwright/blob/bench-deep/bench/deep/RESULTS.md

Why JavaScript can be this fast

V8 compiles hot code to machine code, so tight loops (layout, text measuring) run fast.
The PDF writer streams pages out as they're done, so memory stays flat even at a million rows.
Binary work uses typed arrays, not millions of small objects.

Try it

Demo in your browser: https://mrarun005.github.io/reportwright-demo
Repo: https://github.com/MrArun005/reportwright
PDF library on its own: https://github.com/MrArun005/reportwright-pdf

It's free and MIT-licensed. If you have SSRS or Jasper reports that don't import well, please open an issue. Those are the most useful bug reports I can get.

10 Resume Mistakes That Are Costing You Job Interviews (And How to Fix Them)

Arun Mallikarjuna — Sun, 23 Nov 2025 09:12:31 +0000

Getting job interviews isn’t only about having skills — it’s about showing those skills correctly on your resume.

Even strong candidates lose opportunities because of small, fixable resume mistakes.

After reviewing thousands of resumes, here are the 10 biggest mistakes that silently cost candidates job opportunities — and how to fix them instantly.

💡 Want a resume that is already ATS-friendly and polished? Try Free Resume Pro — it builds professional resumes in minutes: https://free-resumepro.vercel.app

❌ Mistake 1 — Using a Non-ATS-Friendly Format

Many resumes look attractive to humans but fail in ATS (Applicant Tracking Systems).

Bad examples include:

Tables
Text boxes
Headers/footers
Icons instead of bullet points

✔ Fix: Use clean formatting with headings and real text so ATS can scan everything.

❌ Mistake 2 — One Generic Resume for Every Job

Sending the same resume to every company rarely works.

❌ Generic:

Seeking a challenging role in a reputed organization.

✔ Targeted:

Seeking a Data Analyst role focused on SQL, Power BI, and dashboard reporting.

Tailoring = higher keyword match + more interviews.

❌ Mistake 3 — Weak Bullet Points

Most resumes describe responsibilities, not achievements.

❌ Before:
Worked on customer reports.

✔ After:

Built automated weekly customer reports, reducing manual work by 8 hours/week.

Formula:

Action Verb + Task + Result (with numbers)

❌ Mistake 4 — Not Using Industry Keywords

ATS ranks resumes based on keywords from the job description.

Example for Software Engineering:
React, JavaScript, REST API, Git, CI/CD, Agile, Unit Testing

✔ Fix: Study keywords from the job post and include the ones you actually know.

❌ Mistake 5 — Adding Irrelevant Information

Remove fillers such as:

Gender
Age
Full address
Photos
Hobbies (unless job-relevant)

Your resume must show value, not biography.

❌ Mistake 6 — Poor Formatting & Readability

Recruiters scan resumes in 6–8 seconds.

Formatting checklist:

11–12pt font
One font family
Headings + bullet points
Consistent spacing

If your resume looks difficult, the recruiter won’t read it.

❌ Mistake 7 — Typos and Grammar Issues

One typo can ruin the first impression.

Tools:

Grammarly
Hemingway Editor
Spell check

Also: Read your resume aloud — mistakes become easier to spot.

❌ Mistake 8 — No Quantifiable Achievements

Every job has a measurable outcome.

Examples:

% improvement
Time saved
Revenue impact
Cost reduction
Number of users/customers

❌ Before:
Handled customer feedback.

✔ After:
Resolved customer feedback issues, increasing user satisfaction score from 3.8 ⭐ to 4.6 ⭐ within 6 months.

❌ Mistake 9 — Using an Unprofessional Email

Hiring managers notice instantly.

❌ Bad:
cuteboy123@yahoo.com
rockstar_queen@gmail.com

✔ Good:

firstname.lastname@gmail.com

❌ Mistake 10 — Ignoring LinkedIn

When a recruiter likes your resume, the next click is LinkedIn.

Profile must include:

Matching job titles/dates
Skills endorsements
Achievements
Summary aligned with your resume

Add your LinkedIn link in the header of your resume.

⭐ Fastest Way to Fix All 10 Mistakes

You can edit everything manually — but it can take hours.

A faster solution:

Free Resume Pro automatically fixes formatting, bullet points, action verbs, and ATS layout instantly.

Try it here → https://free-resumepro.vercel.app

📝 Final Checklist Before Applying

Requirement	Done?
ATS-friendly	⬜
Tailored for each job	⬜
Strong bullet points	⬜
Keywords added	⬜
Quantifiable achievements	⬜
No irrelevant details	⬜
Formatting consistent	⬜
No grammar errors	⬜
Professional email	⬜
LinkedIn optimized	⬜

💬 Final Thoughts

Fixing these resume mistakes doesn’t just make your resume look better —

it dramatically increases your interview chances.

If you want to skip formatting headaches and build a polished resume instantly, try:
👉 Free Resume Pro — 100% free and ATS-friendly

https://free-resumepro.vercel.app

🔁 Want to support this post?

If you found this useful, please share it with others searching for jobs.

🔥 Hashtags for social media

tags: resume, interview, jobsearch, resumetips