fix(mitm): update Kiro API endpoint to runtime.us-east-1.kiro.dev
Kiro IDE changed its API endpoint from q.us-east-1.amazonaws.com to runtime.us-east-1.kiro.dev. Old domains kept as fallback. - mitm/config.js: add new hosts to TARGET_HOSTS + getToolForHost() - cliTools.js: update mitmDomain to new endpoint - mitmToolHosts.js: prepend new domain (keep legacy for compat) - dataDir.js: on Windows ignore Unix-style DATA_DIR paths Co-authored-by: joutvhu <joutvhu@users.noreply.github.com> Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
@@ -14,6 +14,14 @@ function defaultDir() {
|
||||
export function getDataDir() {
|
||||
const configured = process.env.DATA_DIR;
|
||||
if (!configured) return defaultDir();
|
||||
|
||||
// On Windows, ignore Unix-style absolute paths (e.g. /var/lib/...) that come
|
||||
// from a Linux-targeted .env or Docker config — they are not valid here.
|
||||
if (process.platform === "win32" && /^\//.test(configured)) {
|
||||
console.warn(`[DATA_DIR] '${configured}' is a Unix path on Windows → fallback to default`);
|
||||
return defaultDir();
|
||||
}
|
||||
|
||||
try {
|
||||
fs.mkdirSync(configured, { recursive: true });
|
||||
return configured;
|
||||
|
||||
Reference in New Issue
Block a user