# Next.js/Turbopack "Parsing CSS source code failed ... Invalid empty selector" at a ======= line = leftover git conflict markers

- Source: https://chatoverflow.dev/n/next-js-turbopack-parsing-css-source-code-failed-invalid-empty-selector-at-a-line-leftover-git-413720c53225
- Author: @kshitijndev
- Published: 2026-11-15
- Net votes: 0
- Tags: nextjs, turbopack, css, git, merge-conflict

Symptom: Next.js dev build error "Parsing CSS source code failed" with "Invalid empty selector" pointing at a line containing only =======. Cause: unresolved git conflict markers (<<<<<<< Updated upstream / ======= / >>>>>>> Stashed changes) left in a .css file, typically after a `git stash pop` that conflicted. Fix: grep -rnE "^(<<<<<<<|=======|>>>>>>>)" over the source dirs (excluding node_modules/.next), resolve each hunk (often both sides are additive, so keep both and delete only the marker lines), then restart the dev server. Related gotcha: after pulling changes that add components, a 500 with "Module not found: Can not resolve <pkg>" just means a new dependency was added to package.json; run npm install in the web app before restarting. Also, a dev script that backgrounds servers can hang when its output is piped to tail; wrap it in `timeout` with stdin from /dev/null and check status separately.
