You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected Behavior
Using the lightning web components extension and doing the following in a jest test with ignoring /tests/ through the .forceignore should not cause any problems:
import { createElement } from "lwc";
Actual Behavior:
Using the lightning web components extension and doing the following in a jest test with ignoring /tests/ through the .forceignore CAUSES problems:
import { createElement } from "lwc";
Problem: LWC1702: lwc
Extension version: 60.4.1
VS Code version: Code 1.87.2 (863d2581ecda6849923a2118d93a088b0745d9d6, 2024-03-08T15:20:57.520Z)
OS version: Darwin arm64 23.3.0
Modes:
The text was updated successfully, but these errors were encountered:
@diyer all of your jest test files are marked red with a problem because of the import { createElement } from "lwc"; line. So you loose the overview, if there are real problems and it just looks awful if all files are marked red...
Tests are running fine, it seems just like false linting.
Type: Bug
Expected Behavior
Using the lightning web components extension and doing the following in a jest test with ignoring /tests/ through the .forceignore should not cause any problems:
import { createElement } from "lwc";
Actual Behavior:
Using the lightning web components extension and doing the following in a jest test with ignoring /tests/ through the .forceignore CAUSES problems:
import { createElement } from "lwc";
Problem: LWC1702: lwc
Extension version: 60.4.1
VS Code version: Code 1.87.2 (863d2581ecda6849923a2118d93a088b0745d9d6, 2024-03-08T15:20:57.520Z)
OS version: Darwin arm64 23.3.0
Modes:
The text was updated successfully, but these errors were encountered: