Normalize code frames on thrown errors so that `code` always exists
#5,115 opened on 2020幎9æ8æ¥
Repository metrics
- Stars
- Â (44,030 stars)
- PR merge metrics
-  (30d ã« merged PR ã¯ãããŸãã)
説æ
ð feature request
When using the Parcel API and an error is thrown, there's no guarantee that error.diagnostics.*.codeFrame.code exists. If it doesn't then the consumer of the API has to duplicate this logic to retrieve the code pertaining to the code frame:
This is kind of a pain. I would love to see Parcel normalize these errors so that when a consumer receives a code frame on an error, the code property always exists and the consumer doesn't have to bother with reading source files directly.
ð€ Expected Behavior
I would expect the code property to always exists on any code frame being reported by Parcel.
ð¯ Current Behavior
The code property only sometimes exists on a code frame.
ð Possible Solution
If a plugin doesn't provide the code property, Parcel could add it before the error makes its way to the Parcel consumer.
ðŠ Context
This is described in further detail in https://github.com/parcel-bundler/parcel/discussions/5081.