fix: merge both chromeArgs and chromeArg CLI options

The upstream merge introduced a second CLI option --chromeArg (array)
alongside the existing --chromeArgs (comma-separated string), but
main.ts only read args.chromeArg, silently ignoring --chromeArgs values.
This caused Chrome to launch without critical flags like --no-sandbox,
resulting in "Target closed" errors in sandboxed environments.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: Nima21

.release-please-manifest.json

@@ -1,3 +1,3 @@
 {
-  ".": "0.17.3"
+  ".": "0.17.4"
 }

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "@nimbus21.ai/chrome-devtools-mcp",
-  "version": "0.17.3",
+  "version": "0.17.4",
   "description": "MCP server for Chrome DevTools with stealth mode support",
   "type": "module",
   "bin": "./build/src/index.js",

package.json

@@ -7,13 +7,13 @@
     "url": "https://github.com/ChromeDevTools/chrome-devtools-mcp",
     "source": "github"
   },
-  "version": "0.17.3",
+  "version": "0.17.4",
   "packages": [
     {
       "registryType": "npm",
       "registryBaseUrl": "https://registry.npmjs.org",
       "identifier": "chrome-devtools-mcp",
-      "version": "0.17.3",
+      "version": "0.17.4",
       "transport": {
         "type": "stdio"
       },

server.json

@@ -31,7 +31,7 @@ import {tools} from './tools/tools.js';
 
 // If moved update release-please config
 // x-release-please-start-version
-const VERSION = '0.17.3';
+const VERSION = '0.17.4';
 // x-release-please-end
 
 export const args = parseArguments(VERSION);
@@ -77,7 +77,10 @@ server.server.setRequestHandler(SetLevelRequestSchema, () => {
 
 let context: McpContext;
 async function getContext(): Promise<McpContext> {
-  const chromeArgs: string[] = (args.chromeArg ?? []).map(String);
+  const chromeArgs: string[] = [
+    ...(args.chromeArg ?? []).map(String),
+    ...((args.chromeArgs as string[] | undefined) ?? []).map(String),
+  ];
   const ignoreDefaultChromeArgs: string[] = (
     args.ignoreDefaultChromeArg ?? []
   ).map(String);