From cfa8206a93e404171790d566fd815a5c8d6fa79d Mon Sep 17 00:00:00 2001
From: Jack Li <49817817+Jianxuan-Li@users.noreply.github.com>
Date: Wed, 23 Aug 2023 04:37:20 -0400
Subject: [PATCH] docs(chrome-extensions): remove conflict import (#26631)

---
 docs/src/chrome-extensions-js-python.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/src/chrome-extensions-js-python.md b/docs/src/chrome-extensions-js-python.md
index 30cfc88a68..b9a7af9cdb 100644
--- a/docs/src/chrome-extensions-js-python.md
+++ b/docs/src/chrome-extensions-js-python.md
@@ -102,7 +102,7 @@ To have the extension loaded when running tests you can use a test fixture to se
 First, add fixtures that will load the extension:
 
 ```js title="fixtures.ts"
-import { test as base, expect, chromium, type BrowserContext } from '@playwright/test';
+import { test as base, chromium, type BrowserContext } from '@playwright/test';
 import path from 'path';
 
 export const test = base.extend<{