fix: detect SwiftShader as BLOCKLISTED, not FALLBACK

SwiftShader is Chrome's CPU-based WebGL fallback, used when no GPU
driver is available (CI, Docker, headless browsers, broken drivers).
Consumers need to treat it as tier 0 / BLOCKLISTED so they can fall
back to a non-WebGL experience — cpu-rasterized WebGL is functional
but unusable for anything graphically interesting.

Two bugs combined to make this not work (see #120):

1. The blocklist entry was "google swiftshader", but cleanRenderer
   produces strings like "google, swiftshader ..." (comma between the
   vendor and product). Substring match failed.

2. Renderer strings can legitimately contain punctuation that doesn't
   appear in curated blocklist entries. Relying on exact substring
   match against the raw cleaned string is fragile.

Fixes:

- Shorten the blocklist entry from "google swiftshader" to just
  "swiftshader". SwiftShader is Google-only and always software —
  no false positives to worry about, and it catches future renderer
  string variants that might omit or reorder the vendor prefix.
- Normalize the renderer (strip commas, collapse whitespace) before
  the blocklist substring check so punctuation-only mismatches no
  longer slip through.
- Document `fps` field semantics in the README result-types section:
  it's populated for BENCHMARK and the Apple Silicon FALLBACK only,
  `undefined` for all other types.

Author: puckey

README.md

@@ -69,6 +69,8 @@ Based on the reported `fps` the GPU is then classified into either `tier: 1 (>=
 | `WEBGL_UNSUPPORTED`      | No WebGL context could be created. `tier` is always 0.                              |
 | `SSR`                    | Running server-side — no `window`, detection skipped.                               |
 
+The `fps` field is populated only for `BENCHMARK` results (the measured framerate) and for the Apple Silicon desktop Safari `FALLBACK` (the conservative M1 floor of 60). All other `type` values leave `fps` as `undefined`.
+
 ## API
 
 ```ts

src/index.ts

@@ -320,8 +320,11 @@ export const getGPUTier = async ({
       aDis === bDis ? aFps - bFps : aDis - bDis
     );
   if (!results.length) {
+    // Commas in cleaned renderers (e.g. "google, swiftshader ...") break
+    // substring matches against blocklist entries — strip them first.
+    const renderForBlocklist = renderer!.replace(/,/g, '');
     const blocklistedModel: string | undefined = BLOCKLISTED_GPUS.find(
-      (blocklistedModel) => renderer!.includes(blocklistedModel)
+      (blocklistedModel) => renderForBlocklist.includes(blocklistedModel)
     );
     if (blocklistedModel) return toResult(0, 'BLOCKLISTED', blocklistedModel);
 

src/internal/blocklistedGPUS.ts

@@ -17,7 +17,7 @@ export const BLOCKLISTED_GPUS = [
   'geforce gt 130',
   'geforce gt 330m',
   'geforce gtx 285',
-  'google swiftshader',
+  'swiftshader',
   'intel g41',
   'intel g45',
   'intel gma 4500mhd',

test/index.test.ts

@@ -325,6 +325,19 @@ for (const { input, expected } of [
   });
 });
 
+test('SwiftShader is detected as BLOCKLISTED tier 0', async () => {
+  // SwiftShader is Chrome's CPU-based WebGL fallback — no hardware
+  // acceleration, so consumers should treat it as unusable.
+  const result = await getTier({
+    isMobile: false,
+    renderer:
+      'ANGLE (Google, Vulkan 1.3.0 (SwiftShader Device (Subzero) (0x0000C0DE)), SwiftShader driver)',
+  });
+  expect(result.type).toBe('BLOCKLISTED');
+  expect(result.tier).toBe(0);
+  expect(result.gpu).toBe('swiftshader');
+});
+
 test('Apple Silicon desktop Safari — conservative tier-3 FALLBACK', async () => {
   // Safari returns 'Apple GPU' uniformly for M1–M5 with no chip-level
   // discrimination available from WebGL. Since base M1 already hits the
@@ -402,7 +415,7 @@ test('Apple GPU on mobile does NOT take the desktop tier-3 path', async () => {
   },
   {
     expected: {
-      gpu: 'google swiftshader',
+      gpu: 'swiftshader',
     },
     input: {
       isMobile: false,