AI & Agent Dev Bug Sandbox Back to Radar

MapLibre Worker Fails To Load In Turbopack Due To Unresolved Hashed Chunk Import

When using MapLibre GL v6 with Next.js Turbopack, the generated worker file contains an import for 'maplibre-gl-shared-dev.mjs', but the emitted file has a hash suffix, causing the worker to fail with 'Worker failed to load'.

highConfidence 85%Next.js Affected V16.4.0-Canary.60

Origin Analysis

Turbopack's asset pipeline renames static media chunks with content hashes but fails to rewrite relative imports inside the worker file, so the worker's import of './maplibre-gl-shared-dev.mjs' still points to the un-hashed filename, resulting in a 404 and worker startup failure.

1. Create a new Next.js app using App Router and Turbopack (npx create-next-app@latest). 2. Install maplibre-gl v6, ol, and @geoblocks/ol-maplibre-layer. 3. In a client component, set worker URL: const workerUrl = new URL('maplibre-gl/dist/maplibre-gl-worker.mjs', import.meta.url).toString(); setWorkerUrl(workerUrl); 4. Create a MapLibreLayer and add it to the map. 5. Run `npm run dev --turbopack`. 6. Open the map page; browser console reports 'Worker failed to load'. 7. Inspect .next/dev/static/media/; worker file exists but its import './maplibre-gl-shared-dev.mjs' points to a non-existent file while the hashed version maplibre-gl-shared-dev.<hash>.mjs is present.

Fixing Code Block

0x7F 45 4C 46 02 01 01 000x90 12 AB 04 C1 7E 33 08
0xA4 1C 90 3E 77 0B D2 580x11 F6 6A 2C 80 19 DE 44
0x00 00 00 00 03 00 3E 000x01 00 B7 4D 55 90 0C 61
0x6C 69 62 63 2E 73 6F 2E0x36 00 8E 17 42 AA 05 F3
0xDE C0 DE 01 8B 45 FC 890xC7 5D 20 6F 91 03 E4 78
0x13 37 00 4F 9A 2D E1 700x08 B4 5C 22 71 D0 4A 16
0x48 8D 3D 22 01 00 00 E80x91 FF 0A 63 2E 57 B8 04
0x5A 91 C3 0E 44 70 1B 880x02 6F 39 C4 15 80 ED 27
0xFF 15 40 20 60 00 48 890xC3 90 7A 01 4C 28 B1 56
0x0F 1F 44 00 00 55 48 890xE5 C3 18 6D 92 0B 33 A7

Edge Case Audit

This workaround disables Turbopack, which may reduce development performance and lose Turbopack-specific features. It does not fix the underlying Turbopack bug and should be reverted once an upstream fix is released. Ensure all scripts that previously used --turbopack are updated to avoid inconsistent behavior. For production, verify that worker URLs are correctly served by the chosen bundler. Rollback: restore the original scripts with --turbopack if needed. Alternatively, consider downgrading maplibre-gl to v5.x, which does not require setWorkerUrl.