Errors flagged in vsCode by CF Builder extension

TL;DR: The red squiggle underline is caused, in some way, by the CF Builder extension. It’s wrong, the code and the file are fine, and I want it to go away. Anyone know how to make it go away?

Details:

I installed this extension a few weeks ago, and I didn’t notice (or I ignored) it at the time, but I started getting these red-squiggle notifications on *some* javascript / JSON files. I finally tried narrowing down the problem today, and after blaming it on eslint for a little while, and/or various rules in my project’s `eslintrc.json` file, I disabled all extensions and the error went away.

So I used vsCode’s “Extension Bisector” to find the culprit. I didn’t know this existed till today. Basically it starts by disabling all extensions and reloading your window, and asks you if you can reproduce the problem. You say yes/no, and then it reloads again with some extensions enabled. You repeat the process several times until finally you narrow it down to the culprit extension. It sounds like a PITA but it’s not, it only took a minute. Eventually vsCode told me the extension that was creating the issue, it turned out to be CF Builder (specifically it flagged it as `com-adobe-coldfusion.adobe-cfml-lsp`).

With that disabled, the problem went away. Enabled, the problem returned. I tried going in to the profile settings in CF Builder but I couldn’t find anything as far as linting went. Also note that reproducing is not as simple as just opening any old javascript / JSON file. It seems to lint *specific* files differently. For example `test.json` with the content:

{
	"word": "holmes"
}

had no problem, no red squiggle. But when I renamed that file to `.test.json` and re-opened it, the red squiggle appeared (note that you MUST open the file for the error to show up, and then the file name turns red in the explorer panel). In both cases, the file was correctly identified by vsCode as “JSON”. Similar with a `package.json` file. If I made an exact copy file called `package2.json`, it would not have the problem. But renaming it to `package.json` would cause the squiggle to show up. I also see it happening on a `vite.config.js` file, it underlines the first line’s `import` (not the whole line, just the word `import`).