parcel-bundler/parcel

Build failed. unknown: Error parsing package.json: Unexpected token  in JSON at position 0

Open

#8,378 建立於 2022年8月8日

在 GitHub 查看
 (4 留言) (0 反應) (0 負責人)JavaScript (44,030 star) (2,274 fork)batch import
:bug: Bug:heavy_check_mark: Confirmed Bug:pray: Help WantedGood First Issue

描述

🐛 bug report

🚨 Build failed.

unknown: Error parsing package.json: Unexpected token  in JSON at position 0

this bug for exist 77u/ char for utf8 file. when save package.json with utf8 encoded added 77u/ char in first of content file. parcel json parser need { char for first. Screenshot 2022-08-08 175010

visual studio and many editor always sign utf8 file with 77u/

Software Version(s)
Parcel 2.7.0
Node 18.7.0
npm/Yarn 8.15.0
Operating System windows 11

貢獻者指南

技術棧
javascriptnodejs
領域
build systemdeveloper experience
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
understanding of JSON BOMbasic Node.js file operations
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
70
研究方向
The issue is caused by a UTF 8 BOM (byte order mark) at the start of package.json, which is not handled by Parcel's JSON parser. The fix likely involves stripping the BOM (0xEFBBBF) before parsing. Look at how Parcel reads package.json, probably in src/Config.js or similar files that use JSON.parse. Consider using a utility to remove BOM from file content before parsing, or use a more robust JSON parser. Ensure the fix is applied to all JSON file reads. No linked PRs or assignees, so the issue is open for contribution.