🚀 Feature Proposal

Could it be possible to support an optional case insentive option for query parameters? Adding the option caseSensitive: false does not seems to impact query parameters

Motivation

For backward compatibilitites you sometime need to support multiple casing

Example

With that code

fastify.get<{ Querystring: { test: string } }>(
    "/caseinsensitiv

Expected Behavior

Lozad's browser field in package.json should point to the ES build, as this field is used for bundlers which will then do their own transpilation, tree-shaking, and minification. Pointing at the minified/transpiled build causes this not to happen and results in larger bundle sizes and inability to debug.

Current Behavior

Currently browser points at the minified bui

Describe the bug

It surprised me as well, but apparently NPM is case sensitive

https://www.npmjs.com/package/webStorage
https://www.npmjs.com/package/webstorage

To Reproduce

https://bundlephobia.com/result?p=webStorage

Expected behavior

I should be shown stats for webStorage package, but I see webstorage instead.

Right now they're untrackable

SVG will very likely take a little longer to render than a base64-encoded raster image. And the Gaussian Blur applied to the simple SVG shapes created by Primitive is probably quite CPU intensive.

Let's run a series of performance tests, ideally on WPT, to compare LQIP raster image rendering performance vs. SQIP rendering performance and also compare CPU utilization.

when browsing, i should be able to perf-check right from the browser and results should be siphoned back to the extension.