Menu

Post image 1
Post image 2
1 / 2
0

How a missing @ in a filename broke my Netlify build

DEV Community·Osmium·about 1 month ago
#KEupdEZA
#webdev#netlify#javascript#file#path#qwik
Reading 0:00
15s threshold

It was fine three months ago :( Three months ago I deployed my Qwik site to Netlify. And after some while, I pushed an new, unrelated content change and the build died without touching a thing on it’s codebase: Edge Functions bundling ──────────────────────────────────────────────────────────────── Packaging Edge Functions from .netlify/edge-functions directory: - entry.netlify-edge [Error: ENOENT: no such file or directory, stat '/tmp/tmp-2269-6qAdCcbGEFml/qwik-city-not-found-paths.js'] { errno: -2, code: 'ENOENT', syscall: 'stat', path: '/tmp/tmp-2269-6qAdCcbGEFml/qwik-city-not-found-paths.js' } Node.js v22.22.1 Enter fullscreen mode Exit fullscreen mode No version bumps in package.json . No config changes. The build itself (client, server) compiled cleanly. If it worked three months ago with the exact same versions, why was it broken now? I did the usual steps: Cleared cache and ran the build, failed. But build process worked fine on local machine.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More