Understanding how compression middleware works

[macbruker]

I've been experimenting with adding compression middleware to the new eleventy-dev-server. Mostly so I can see how tiny I am able to keep my project footprint while running it locally 😁. Here is what that looks like in my eleventy.config.js file:

(eleventy 2.0.0-canary.16)

const compression = require("compression");

module.exports = function (eleventyConfig) {
  eleventyConfig.setServerOptions({
    enabled: true,
    showVersion: true,
    port: 8888,
    middleware: [compression()],
  });
}

This works most of the time without issues. But some times i get this error message:

[dev:*eleventy] [11ty] Uncaught exception: (more in DEBUG output)
[dev:*eleventy] [11ty] Cannot set headers after they are sent to the client (via Error)
[dev:*eleventy] [11ty] 
[dev:*eleventy] [11ty] Original error stack trace: Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
[dev:*eleventy] [11ty]     at new NodeError (node:internal/errors:387:5)
[dev:*eleventy] [11ty]     at ServerResponse.setHeader (node:_http_outgoing:603:11)
[dev:*eleventy] [11ty]     at ServerResponse.resp.end (/Users/martin/Sites/my-project/node_modules/@11ty/eleventy-dev-server/server/wrapResponse.js:102:16)
[dev:*eleventy] [11ty]     at ServerResponse.end (/Users/martin/Sites/my-project/node_modules/compression/index.js:107:21)
[dev:*eleventy] [11ty]     at write (/Users/martin/Sites/my-project/node_modules/finalhandler/index.js:302:9)
[dev:*eleventy] [11ty]     at AsyncResource.runInAsyncScope (node:async_hooks:203:9)
[dev:*eleventy] [11ty]     at listener (/Users/martin/Sites/my-project/node_modules/on-finished/index.js:170:15)
[dev:*eleventy] [11ty]     at onFinish (/Users/martin/Sites/my-project/node_modules/on-finished/index.js:101:5)
[dev:*eleventy] [11ty]     at callback (/Users/martin/Sites/my-project/node_modules/ee-first/index.js:55:10)
[dev:*eleventy] [11ty]     at IncomingMessage.onevent (/Users/martin/Sites/my-project/node_modules/ee-first/index.js:93:5)

I'm guessing this is because of the order of when stuff is executed. Maybe trying to run compression on something that does not exist yet. I am looking for help to understand the error and tips for a better way to configure the compression middleware.