[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"verticals":3,"quiz-compressionstream-native-gzip":32,"quiz-article-compressionstream-native-gzip":48},[4,20],{"id":5,"slug":6,"name":7,"tagline":8,"description":9,"accentFrom":10,"accentTo":11,"icon":12,"defaultLocale":13,"locales":14,"features":16,"position":19},"019fe637-3d33-714b-b57f-23e163ffca0c","dev","Web Development","Build. Learn. Ship.","Practical courses, engineering-grade articles and open-source tools for people who ship.","violet-500","cyan-400","◇","en",[13,15],"fa",{"courses":17,"paths":17,"articles":17,"exams":18,"flashcards":18,"packages":17,"community":17,"certificates":17,"teams":17,"commerce":17},true,false,0,{"id":21,"slug":22,"name":23,"tagline":24,"description":25,"accentFrom":26,"accentTo":10,"icon":27,"defaultLocale":13,"locales":28,"features":30,"position":31},"019fe637-3dc2-754c-8657-0f175bfee7c6","lang","Languages","Learn a language the way you learn a codebase.","Structured paths, listening drills and spaced repetition that actually sticks.","amber-400","⌘",[13,15,29],"es",{"courses":17,"paths":17,"articles":18,"exams":18,"flashcards":18,"packages":18,"community":17,"certificates":18,"teams":18,"commerce":17},2,{"id":33,"slug":34,"kind":35,"title":36,"description":37,"config":38,"verticalId":5,"vertical":43,"course":40,"_count":44,"access":45,"attempts":47,"questionCount":39},"019ff19b-f5e9-74ff-8f5c-5feaea317066","compressionstream-native-gzip","PRACTICE_QUIZ","CompressionStream — native gzip without pako","CompressionStream and DecompressionStream are native browser APIs for compressing and decompressing data in gzip, deflate, and deflate-raw formats — no library required. These questions cover the API shape, supported formats, how to use the Streams plumbing, what it replaces, and where it works.",{"questionCount":39,"timeLimitSec":40,"shuffleQuestions":18,"shuffleOptions":17,"negativeMarking":19,"passScorePct":41,"maxAttempts":40,"revealAnswers":42,"allowFlagging":18,"allowBacktracking":17},9,null,70,"AFTER_SUBMIT",{"slug":6,"name":7},{"questions":39},{"allowed":17,"reason":46},"FREE",[],{"id":49,"slug":34,"title":50,"subtitle":40,"excerpt":51,"coverUrl":52,"locale":13,"readingMinutes":53,"publishedAt":54,"viewCount":55,"likeCount":19,"commentCount":19,"author":56,"vertical":61,"topic":62,"tags":65,"_count":77,"playground":79,"body":81,"bodyMd":259,"seo":260,"translationGroupId":264,"thread":265,"assessments":267,"translations":270,"quiz":272},"019ff19b-f5b3-7569-8cc8-22b1136aa9b2","You're importing pako to gzip data. `CompressionStream` does it natively.","pako is one of npm's most downloaded packages — pulled in by thousands of projects to compress data before storing or sending it. CompressionStream and DecompressionStream do the same job natively, in any modern browser and Node.js 18+, with no dependencies and native C-speed execution.","\u002Fmedia\u002Fcovers\u002Fcompressionstream-native-gzip.png",4,"2026-08-10T07:49:27.000Z",54,{"id":57,"name":58,"username":59,"avatarUrl":40,"headline":60},"019fe637-3c25-7088-9034-39c9f15dc3c8","Parsa Jiravand","parsa","Frontend engineer · building bestpractic",{"slug":6,"name":7,"accentFrom":10,"accentTo":11},{"slug":63,"name":64},"javascript","JavaScript",[66,68,71,74],{"slug":63,"name":67,"color":40},"Javascript",{"slug":69,"name":70,"color":40},"webdev","Webdev",{"slug":72,"name":73,"color":40},"frontend","Frontend",{"slug":75,"name":76,"color":40},"performance","Performance",{"assessments":78},1,{"slug":34,"title":80},"CompressionStream — interactive playground",{"blocks":82,"version":78},[83,87,91,94,100,103,107,110,114,117,120,123,127,130,133,136,140,143,146,150,153,156,159,179,182,184,187,194,197,200,203,206,209,212,215,218,221,224,227,230,233,236,239,242,245,248,251],{"id":84,"html":85,"type":86},"b1","\u003Cp>Compressing data before writing it to IndexedDB or sending it over a slow connection is a real optimization. When a cached API response is too large for reliable storage, or when you need to shrink a JSON payload before POSTing it, \u003Ccode>pako.gzip()\u003C\u002Fcode> is the standard reach. But pako is a pure-JavaScript port of zlib — written in user space to fill a gap the browser had at the time. The \u003Ccode>CompressionStream\u003C\u002Fcode> API is that gap closing.\u003C\u002Fp>","paragraph",{"id":88,"html":89,"text":89,"type":90,"level":31},"b2","The API","heading",{"id":92,"html":93,"type":86},"b3","\u003Cp>\u003Ccode>CompressionStream\u003C\u002Fcode> is a \u003Ca href=\"https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FWeb\u002FAPI\u002FTransformStream\">transform stream\u003C\u002Fa> — data goes in one end, compressed data comes out the other. The constructor takes a format string: \u003Ccode>'gzip'\u003C\u002Fcode>, \u003Ccode>'deflate'\u003C\u002Fcode>, or \u003Ccode>'deflate-raw'\u003C\u002Fcode>.\u003C\u002Fp>",{"id":95,"code":96,"type":97,"language":98,"highlight":99},"b4","const stream = new CompressionStream('gzip');","code","js",[],{"id":101,"html":102,"type":86},"b5","\u003Cp>\u003Ccode>DecompressionStream\u003C\u002Fcode> is the mirror:\u003C\u002Fp>",{"id":104,"code":105,"type":97,"language":98,"highlight":106},"b6","const stream = new DecompressionStream('gzip');",[],{"id":108,"html":109,"type":86},"b7","\u003Cp>The Streams plumbing to feed data in and collect it out is the verbose part. Wrap it once:\u003C\u002Fp>",{"id":111,"code":112,"type":97,"language":98,"highlight":113},"b8","async function compress(input, format = 'gzip') {\n  const stream = new Blob([input]).stream().pipeThrough(new CompressionStream(format));\n  return new Uint8Array(await new Response(stream).arrayBuffer());\n}\n\nasync function decompress(input, format = 'gzip') {\n  const stream = new Blob([input]).stream().pipeThrough(new DecompressionStream(format));\n  return new Response(stream).text();\n}",[],{"id":115,"html":116,"type":86},"b9","\u003Cp>\u003Ccode>Blob.stream().pipeThrough()\u003C\u002Fcode> feeds the data into the transform stream; \u003Ccode>new Response(stream)\u003C\u002Fcode> collects the result. The idiom is three lines of plumbing written once, then call sites that read plainly.\u003C\u002Fp>",{"id":118,"html":119,"text":119,"type":90,"level":31},"b10","Replacing pako",{"id":121,"html":122,"type":86},"b11","\u003Cp>A direct swap for the most common pako usage patterns:\u003C\u002Fp>",{"id":124,"code":125,"type":97,"language":98,"highlight":126},"b12","\u002F\u002F Before — pako\nimport pako from 'pako';\n\nconst compressed = pako.gzip(jsonString);       \u002F\u002F Uint8Array\nconst restored   = pako.ungzip(compressed, { to: 'string' });\n\n\u002F\u002F After — native\nconst compressed = await compress(jsonString);           \u002F\u002F Uint8Array\nconst restored   = await decompress(compressed);         \u002F\u002F string",[],{"id":128,"html":129,"type":86},"b13","\u003Cp>The output is the same gzip-format \u003Ccode>Uint8Array\u003C\u002Fcode>. Any system that accepts pako's output accepts the native output — the wire format is identical.\u003C\u002Fp>",{"id":131,"html":132,"text":132,"type":90,"level":31},"b14","Real-world patterns",{"id":134,"html":135,"type":86},"b15","\u003Cp>\u003Cstrong>Storing large JSON in IndexedDB:\u003C\u002Fstrong>\u003C\u002Fp>",{"id":137,"code":138,"type":97,"language":98,"highlight":139},"b16","async function putCompressed(store, key, data) {\n  const compressed = await compress(JSON.stringify(data));\n  return store.put(compressed, key);\n}\n\nasync function getCompressed(store, key) {\n  const compressed = await store.get(key);\n  if (!compressed) return null;\n  return JSON.parse(await decompress(compressed));\n}",[],{"id":141,"html":142,"type":86},"b17","\u003Cp>A 200 KB JSON object typically compresses to 15–30 KB with gzip. For quota-constrained storage like IndexedDB on mobile browsers, that difference matters.\u003C\u002Fp>",{"id":144,"html":145,"type":86},"b18","\u003Cp>\u003Cstrong>Compressing in a Web Worker:\u003C\u002Fstrong>\u003C\u002Fp>",{"id":147,"code":148,"type":97,"language":98,"highlight":149},"b19","\u002F\u002F worker.js\nself.onmessage = async ({ data }) => {\n  const compressed = await compress(JSON.stringify(data.payload));\n  self.postMessage({ compressed }, [compressed.buffer]);\n};",[],{"id":151,"html":152,"type":86},"b20","\u003Cp>\u003Ccode>CompressionStream\u003C\u002Fcode> works in Web Workers and Service Workers — the same API, the same two-function wrapper, no restrictions. Offloading compression to a worker keeps the main thread free.\u003C\u002Fp>",{"id":154,"html":155,"text":155,"type":90,"level":31},"b21","Format reference",{"id":157,"html":158,"type":86},"b22","\u003Cp>The three supported formats map directly to pako's methods:\u003C\u002Fp>",{"id":160,"head":161,"rows":165,"type":178},"b23",[162,163,164],"\u003Ccode>CompressionStream\u003C\u002Fcode> format","pako equivalent","When to use",[166,170,174],[167,168,169],"\u003Ccode>'gzip'\u003C\u002Fcode>","\u003Ccode>pako.gzip\u003C\u002Fcode> \u002F \u003Ccode>pako.ungzip\u003C\u002Fcode>","HTTP transport, file storage — the standard",[171,172,173],"\u003Ccode>'deflate'\u003C\u002Fcode>","\u003Ccode>pako.deflate\u003C\u002Fcode> \u002F \u003Ccode>pako.inflate\u003C\u002Fcode>","zlib-wrapped deflate",[175,176,177],"\u003Ccode>'deflate-raw'\u003C\u002Fcode>","\u003Ccode>pako.deflateRaw\u003C\u002Fcode> \u002F \u003Ccode>pako.inflateRaw\u003C\u002Fcode>","raw DEFLATE, no wrapper header","table",{"id":180,"html":181,"type":86},"b24","\u003Cp>\u003Ccode>'gzip'\u003C\u002Fcode> is the right default for most use cases. Use \u003Ccode>'deflate-raw'\u003C\u002Fcode> only when interoperating with a system that expects unwrapped DEFLATE.\u003C\u002Fp>",{"id":183,"html":76,"text":76,"type":90,"level":31},"b25",{"id":185,"html":186,"type":86},"b26","\u003Cp>\u003Ccode>CompressionStream\u003C\u002Fcode> calls into the browser's native zlib implementation — the same C code path used when the browser decompresses HTTP responses with \u003Ccode>Content-Encoding: gzip\u003C\u002Fcode>. pako re-implements that algorithm in JavaScript. The native path is measurably faster on large inputs:\u003C\u002Fp>",{"id":188,"type":189,"items":190,"ordered":18},"b27","list",[191,192,193],"For small payloads (< 10 KB), the difference is negligible.","For large payloads (100 KB+), native compression is typically 3–10× faster than pako, because there's no JavaScript overhead and the engine can use SIMD instructions.","There's also no bundle cost: pako adds ~45 KB minified to your bundle; \u003Ccode>CompressionStream\u003C\u002Fcode> adds zero.",{"id":195,"html":196,"text":196,"type":90,"level":31},"b28","Node.js",{"id":198,"html":199,"type":86},"b29","\u003Cp>\u003Ccode>CompressionStream\u003C\u002Fcode> and \u003Ccode>DecompressionStream\u003C\u002Fcode> are available in \u003Cstrong>Node.js 18.0\u003C\u002Fstrong> as part of the Web Streams implementation. The two-function wrapper above works unchanged in Node 18+ — useful for isomorphic utilities that run in both browser and server environments without branching on the environment.\u003C\u002Fp>",{"id":201,"html":202,"type":86},"b30","\u003Cp>Node's older \u003Ccode>zlib\u003C\u002Fcode> module (\u003Ccode>zlib.gzipSync\u003C\u002Fcode>, \u003Ccode>zlib.gunzipSync\u003C\u002Fcode>) is still more ergonomic for Node-only server code. But if you're writing a shared utility that must work in both contexts, \u003Ccode>CompressionStream\u003C\u002Fcode> is the right choice.\u003C\u002Fp>",{"id":204,"html":205,"text":205,"type":90,"level":31},"b31","Browser support",{"id":207,"html":208,"type":86},"b32","\u003Cp>\u003Ccode>CompressionStream\u003C\u002Fcode> is \u003Cstrong>Baseline 2023\u003C\u002Fstrong>: Chrome 80 (February 2020), Firefox 113 (May 2023), Safari 16.4 (March 2023), Node.js 18. The API has been in Chromium since early 2020; Firefox and Safari joined in 2023. It's available in all currently-supported browser and runtime versions, including Web Workers and Service Workers.\u003C\u002Fp>",{"id":210,"html":211,"type":86},"b33","\u003C!-- playground:start -->",{"id":213,"html":214,"text":214,"type":90,"level":31},"b34","🎮 Try it yourself",{"id":216,"html":217,"type":86},"b35","\u003Cp>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fdaily-post-dev.netlify.app\u002Fposts\u002F2026-08-10-compressionstream-native-gzip\u002Fplayground\u002F\">▶️ Open the interactive playground →\u003C\u002Fa>\u003C\u002Fstrong>\u003C\u002Fp>",{"id":219,"html":220,"type":86},"b36","\u003Cp>\u003Cem>Runs right in your browser — poke at it and watch the concept react live.\u003C\u002Fem>\u003C\u002Fp>",{"id":222,"html":223,"type":86},"b37","\u003C!-- playground:end -->",{"id":225,"html":226,"type":86},"b38","\u003C!-- quiz:start -->",{"id":228,"html":229,"text":229,"type":90,"level":31},"b39","🧠 Test yourself",{"id":231,"html":232,"type":86},"b40","\u003Cp>Think it clicked? \u003Cstrong>\u003Ca href=\"https:\u002F\u002Fdaily-post-dev.netlify.app\u002Fquiz\u002Ftake.html?post=2026-08-10-compressionstream-native-gzip\">Take the 9-question quiz →\u003C\u002Fa>\u003C\u002Fstrong>\u003C\u002Fp>",{"id":234,"html":235,"type":86},"b41","\u003Cp>\u003Cem>Instant feedback, a hint on every question, and an explanation for each answer — right or wrong.\u003C\u002Fem>\u003C\u002Fp>",{"id":237,"html":238,"type":86},"b42","\u003C!-- quiz:end -->",{"id":240,"html":241,"text":241,"type":90,"level":31},"b43","The takeaway",{"id":243,"html":244,"type":86},"b44","\u003Cp>Search your \u003Ccode>package.json\u003C\u002Fcode> for \u003Ccode>pako\u003C\u002Fcode>. If it's there and the use case is "compress a string or buffer before storing or sending it," the native API covers you. Replace \u003Ccode>pako.gzip\u003C\u002Fcode> and \u003Ccode>pako.ungzip\u003C\u002Fcode> with the two-function wrapper above, remove the dependency, and get native compression speed and zero bundle cost. The Streams API is verbose on its own — the wrapper absorbs that cost once so every call site stays clean.\u003C\u002Fp>",{"id":246,"type":247},"b45","divider",{"id":249,"html":250,"type":86},"b46","\u003Cp>\u003Cem>Thanks for reading! Let's stay connected:\u003C\u002Fem>\u003C\u002Fp>",{"id":252,"type":189,"items":253,"ordered":18},"b47",[254,255,256,257,258],"⭐ \u003Cstrong>GitHub\u003C\u002Fstrong> — follow me and star the projects: \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fparsajiravand\">github.com\u002Fparsajiravand\u003C\u002Fa>","💬 \u003Cstrong>Discord\u003C\u002Fstrong> — join the frontend best-practices community: \u003Ca href=\"https:\u002F\u002Fdiscord.gg\u002Fd9KRhuAwQ\">discord.gg\u002Fd9KRhuAwQ\u003C\u002Fa>","📸 \u003Cstrong>Instagram\u003C\u002Fstrong> — frontend best practices, daily: \u003Ca href=\"https:\u002F\u002Fwww.instagram.com\u002Fbestpractice___\u002F\">@bestpractice___\u003C\u002Fa>","💼 \u003Cstrong>LinkedIn\u003C\u002Fstrong> — \u003Ca href=\"https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fparsa-jiravand\u002F\">linkedin.com\u002Fin\u002Fparsa-jiravand\u003C\u002Fa>","✉️ \u003Cstrong>Email\u003C\u002Fstrong> (work & contract inquiries): \u003Ca href=\"mailto:bestpractice2026@gmail.com\">bestpractice2026@gmail.com\u003C\u002Fa>","Compressing data before writing it to IndexedDB or sending it over a slow connection is a real optimization. When a cached API response is too large for reliable storage, or when you need to shrink a JSON payload before POSTing it, `pako.gzip()` is the standard reach. But pako is a pure-JavaScript port of zlib — written in user space to fill a gap the browser had at the time. The `CompressionStream` API is that gap closing.\n\n## The API\n\n`CompressionStream` is a [transform stream](https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FWeb\u002FAPI\u002FTransformStream) — data goes in one end, compressed data comes out the other. The constructor takes a format string: `'gzip'`, `'deflate'`, or `'deflate-raw'`.\n\n```js\nconst stream = new CompressionStream('gzip');\n```\n\n`DecompressionStream` is the mirror:\n\n```js\nconst stream = new DecompressionStream('gzip');\n```\n\nThe Streams plumbing to feed data in and collect it out is the verbose part. Wrap it once:\n\n```js\nasync function compress(input, format = 'gzip') {\n  const stream = new Blob([input]).stream().pipeThrough(new CompressionStream(format));\n  return new Uint8Array(await new Response(stream).arrayBuffer());\n}\n\nasync function decompress(input, format = 'gzip') {\n  const stream = new Blob([input]).stream().pipeThrough(new DecompressionStream(format));\n  return new Response(stream).text();\n}\n```\n\n`Blob.stream().pipeThrough()` feeds the data into the transform stream; `new Response(stream)` collects the result. The idiom is three lines of plumbing written once, then call sites that read plainly.\n\n## Replacing pako\n\nA direct swap for the most common pako usage patterns:\n\n```js\n\u002F\u002F Before — pako\nimport pako from 'pako';\n\nconst compressed = pako.gzip(jsonString);       \u002F\u002F Uint8Array\nconst restored   = pako.ungzip(compressed, { to: 'string' });\n\n\u002F\u002F After — native\nconst compressed = await compress(jsonString);           \u002F\u002F Uint8Array\nconst restored   = await decompress(compressed);         \u002F\u002F string\n```\n\nThe output is the same gzip-format `Uint8Array`. Any system that accepts pako's output accepts the native output — the wire format is identical.\n\n## Real-world patterns\n\n**Storing large JSON in IndexedDB:**\n\n```js\nasync function putCompressed(store, key, data) {\n  const compressed = await compress(JSON.stringify(data));\n  return store.put(compressed, key);\n}\n\nasync function getCompressed(store, key) {\n  const compressed = await store.get(key);\n  if (!compressed) return null;\n  return JSON.parse(await decompress(compressed));\n}\n```\n\nA 200 KB JSON object typically compresses to 15–30 KB with gzip. For quota-constrained storage like IndexedDB on mobile browsers, that difference matters.\n\n**Compressing in a Web Worker:**\n\n```js\n\u002F\u002F worker.js\nself.onmessage = async ({ data }) => {\n  const compressed = await compress(JSON.stringify(data.payload));\n  self.postMessage({ compressed }, [compressed.buffer]);\n};\n```\n\n`CompressionStream` works in Web Workers and Service Workers — the same API, the same two-function wrapper, no restrictions. Offloading compression to a worker keeps the main thread free.\n\n## Format reference\n\nThe three supported formats map directly to pako's methods:\n\n| `CompressionStream` format | pako equivalent | When to use |\n|---|---|---|\n| `'gzip'` | `pako.gzip` \u002F `pako.ungzip` | HTTP transport, file storage — the standard |\n| `'deflate'` | `pako.deflate` \u002F `pako.inflate` | zlib-wrapped deflate |\n| `'deflate-raw'` | `pako.deflateRaw` \u002F `pako.inflateRaw` | raw DEFLATE, no wrapper header |\n\n`'gzip'` is the right default for most use cases. Use `'deflate-raw'` only when interoperating with a system that expects unwrapped DEFLATE.\n\n## Performance\n\n`CompressionStream` calls into the browser's native zlib implementation — the same C code path used when the browser decompresses HTTP responses with `Content-Encoding: gzip`. pako re-implements that algorithm in JavaScript. The native path is measurably faster on large inputs:\n\n- For small payloads (\u003C 10 KB), the difference is negligible.\n- For large payloads (100 KB+), native compression is typically 3–10× faster than pako, because there's no JavaScript overhead and the engine can use SIMD instructions.\n- There's also no bundle cost: pako adds ~45 KB minified to your bundle; `CompressionStream` adds zero.\n\n## Node.js\n\n`CompressionStream` and `DecompressionStream` are available in **Node.js 18.0** as part of the Web Streams implementation. The two-function wrapper above works unchanged in Node 18+ — useful for isomorphic utilities that run in both browser and server environments without branching on the environment.\n\nNode's older `zlib` module (`zlib.gzipSync`, `zlib.gunzipSync`) is still more ergonomic for Node-only server code. But if you're writing a shared utility that must work in both contexts, `CompressionStream` is the right choice.\n\n## Browser support\n\n`CompressionStream` is **Baseline 2023**: Chrome 80 (February 2020), Firefox 113 (May 2023), Safari 16.4 (March 2023), Node.js 18. The API has been in Chromium since early 2020; Firefox and Safari joined in 2023. It's available in all currently-supported browser and runtime versions, including Web Workers and Service Workers.\n\n\n\u003C!-- playground:start -->\n\n## 🎮 Try it yourself\n\n**[▶️ Open the interactive playground →](https:\u002F\u002Fdaily-post-dev.netlify.app\u002Fposts\u002F2026-08-10-compressionstream-native-gzip\u002Fplayground\u002F)**\n\n_Runs right in your browser — poke at it and watch the concept react live._\n\n\u003C!-- playground:end -->\n\n\u003C!-- quiz:start -->\n\n## 🧠 Test yourself\n\nThink it clicked? **[Take the 9-question quiz →](https:\u002F\u002Fdaily-post-dev.netlify.app\u002Fquiz\u002Ftake.html?post=2026-08-10-compressionstream-native-gzip)**\n\n_Instant feedback, a hint on every question, and an explanation for each answer — right or wrong._\n\n\u003C!-- quiz:end -->\n## The takeaway\n\nSearch your `package.json` for `pako`. If it's there and the use case is \"compress a string or buffer before storing or sending it,\" the native API covers you. Replace `pako.gzip` and `pako.ungzip` with the two-function wrapper above, remove the dependency, and get native compression speed and zero bundle cost. The Streams API is verbose on its own — the wrapper absorbs that cost once so every call site stays clean.\n\n---\n\n*Thanks for reading! Let's stay connected:*\n\n- ⭐ **GitHub** — follow me and star the projects: [github.com\u002Fparsajiravand](https:\u002F\u002Fgithub.com\u002Fparsajiravand)\n- 💬 **Discord** — join the frontend best-practices community: [discord.gg\u002Fd9KRhuAwQ](https:\u002F\u002Fdiscord.gg\u002Fd9KRhuAwQ)\n- 📸 **Instagram** — frontend best practices, daily: [@bestpractice___](https:\u002F\u002Fwww.instagram.com\u002Fbestpractice___\u002F)\n- 💼 **LinkedIn** — [linkedin.com\u002Fin\u002Fparsa-jiravand](https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fparsa-jiravand\u002F)\n- ✉️ **Email** (work & contract inquiries): [bestpractice2026@gmail.com](mailto:bestpractice2026@gmail.com)",{"title":261,"canonical":262,"description":263},"You're importing pako to gzip data. `CompressionStream` does it native","https:\u002F\u002Fbestpractic.org\u002Fblog\u002Fcompressionstream-native-gzip","pako is one of npm's most downloaded packages — pulled in by thousands of projects to compress data before storing or sending it. CompressionStream and DecompressionStream do the s","019ff19b-f5b3-7569-8cc8-26ce3d003b46",{"id":266,"locked":18},"019ff19b-f5cd-72ed-b408-85e7f5a92070",[268],{"id":33,"slug":34,"title":36,"_count":269},{"questions":39},[271],{"locale":13,"slug":34},{"id":33,"slug":34,"title":36,"_count":273,"questionCount":39},{"questions":39}]