Add @ts-ignore to Image.js as TS6 forbids untyped side-effect imports

R=kimanh@chromium.org

Bug: 503111303,502804868
Change-Id: Ib472dfb87341cac90f4cbec9dc97aa6cc5ceb28b
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/7767789
Auto-Submit: Simon Zünd <szuend@chromium.org>
Commit-Queue: Kim-Anh Tran <kimanh@chromium.org>
Reviewed-by: Kim-Anh Tran <kimanh@chromium.org>

Author: szuend

front_end/entrypoints/device_mode_emulation_frame/device_mode_emulation_frame.ts

@@ -3,6 +3,10 @@
 // found in the LICENSE file.
 
 import '../../core/dom_extension/dom_extension.js';
+// eslint-disable-next-line @typescript-eslint/ban-ts-comment
+// @ts-ignore: tsc 6.0 does not support side-effect imports without a type definition.
+// We cannot use `@ts-expect-error` here because the import is correctly resolved
+// when bundling the application (which doesn't error) and only errors in unbundled builds.
 import '../../Images/Images.js';
 
 if (window.opener) {

front_end/entrypoints/shell/shell.ts

@@ -2,6 +2,10 @@
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
+// eslint-disable-next-line @typescript-eslint/ban-ts-comment
+// @ts-ignore: tsc 6.0 does not support side-effect imports without a type definition.
+// We cannot use `@ts-expect-error` here because the import is correctly resolved
+// when bundling the application (which doesn't error) and only errors in unbundled builds.
 import '../../Images/Images.js';
 import '../../core/dom_extension/dom_extension.js';
 import '../../panels/sources/sources-meta.js';

front_end/entrypoints/trace_app/trace_app.ts

@@ -6,6 +6,10 @@ import '../main/main-meta.js';
 import '../inspector_main/inspector_main-meta.js';
 import '../../core/sdk/sdk-meta.js';
 import '../../models/workspace/workspace-meta.js';
+// eslint-disable-next-line @typescript-eslint/ban-ts-comment
+// @ts-ignore: tsc 6.0 does not support side-effect imports without a type definition.
+// We cannot use `@ts-expect-error` here because the import is correctly resolved
+// when bundling the application (which doesn't error) and only errors in unbundled builds.
 import '../../Images/Images.js';
 import '../../models/logs/logs-meta.js';
 import '../../models/persistence/persistence-meta.js';