BatemanVO

@pmdartus @trevor-bliss I'm actually having trouble finding said mapping that @dominic-butlerSFDC mentioned, I agree it would be nice to be in the repo somewhere. Our SF instance also just upgraded...

Our Org is now on API v51, but installing `sfdx-lwc-jest` version 0.11.0, which, [from the versions tab on the NPM website](https://www.npmjs.com/package/@salesforce/sfdx-lwc-jest), is the latest version, I receive the error: ```error...

I copy/pasted the code and ran the test and both pass for me: ``` PASS force-app/main/default/lwc/customComponent/__tests__/customComponent.test.js custom component test √ connectedCallback (143 ms) √ customMethod (15 ms) Test Suites: 1...

Starting on Nov. 16 with [this post](https://github.com/istanbuljs/istanbuljs/issues/516#issuecomment-971265354) in this thread, the topic was actually subtly changed - the original issue was that optional chaining is _not_ creating branches that need...

As requested from the previous thread: VS Code Version: 1.86.2, x64 SFDX CLI Version: 2.29.5 OS and version: Windows 10 22H2 Build 19045.4046

Our team was on v1.3.0 and just updated to v1.4.1 today, but began encountering the same issue sporadically with any comments whatsoever before import statements. It doesn't occur on all...

@nolanlawson [Here is a link to a barebones repo where I can reproduce the issue](https://github.com/BatemanVO/demo-sfdx-lwc-jest-coverage-issue). Here is the coverage reported with the comment left at the top of the file:...

Just updated a couple of our repos to sfdx-lwc-jest 4.0.1 today and still encountering the same issue. Some files that were not affected with version 3.0.1 were affected after updating...

Still seeing the issue with sfdx-lwc-jest 5.0.0 as of today, though have noticed a slight change in behavior. The coverage tool still reports comments before import statements as uncovered, but...