We're rolling out this change from Chrome 147 (starting to roll out next week): https://chromestatus.com/feature/6330376953921536
Which will add two new values (16 and 32) to the values that can be returned by navigator.deviceMemory. I suggest you include these in your script and README (let me know if you want a PR).
We're also dropping some values at the lower end, but since older Chrome (and other Chromium) browsers will still report those you can't drop them yet.
Also if you are aware of are aware of any other checks like this, then I'd love to hear. I've already had Castle update their blog post which I think is where you got this from based on the README.md file.
We're rolling out this change from Chrome 147 (starting to roll out next week): https://chromestatus.com/feature/6330376953921536
Which will add two new values (16 and 32) to the values that can be returned by
navigator.deviceMemory. I suggest you include these in your script and README (let me know if you want a PR).We're also dropping some values at the lower end, but since older Chrome (and other Chromium) browsers will still report those you can't drop them yet.
Also if you are aware of are aware of any other checks like this, then I'd love to hear. I've already had Castle update their blog post which I think is where you got this from based on the README.md file.