Errors should tell me _where_ the error is

🐛 bug report

I get errors stating a problem, but not where it was encountered.

$ npx parcel build index.html things/**/index.html 

(This one was a left-over unpkg.com import in a JS file)

(This one was in a SVG file. Gonna file another bug for this)

🌍 Your Environment

Software	Version(s)
Parcel	2.0.0-beta.1
Node	v14.9.0
npm/Yarn	npm@6.14.9
Operating System	MacOS 10.15.7

[mischnic]

For terser, we use sourcemaps to convert the error location back to the source. But this isn’t always possible and there are furthermore no HTML sorucemaps…

that could be done more generally

But I’m convinced 😄 -> https://github.com/parcel-bundler/parcel/issues/5477

deleting .parcel-cache didn’t solve the issue here for me.

Any chance you can post a reproduction?

[surma]

Another one. It tells me line and character, but not which file.

But this error is either caused by a malfunctioning plugin or a Parcel bug (probably the same as #5311). You probably expected a file path to be printed?

I don’t know — I guess that’s kind of the problem. Fwiw, unlike #5311, deleting .parcel-cache didn’t solve the issue here for me.