Login works

backend/node_modules/cross-env/LICENSE

@@ -0,0 +1,20 @@
+The MIT License (MIT)
+Copyright (c) 2017-2025 Kent C. Dodds
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

backend/node_modules/cross-env/README.md

@@ -0,0 +1,194 @@
+<div align="center">
+<h1>cross-env 🔀</h1>
+
+<p>Run scripts that set and use environment variables across platforms</p>
+</div>
+
+**🎉 NOTICE: cross-env is "done" as in it does what it does and there's no need
+for new features.
+[Learn more](https://github.com/kentcdodds/cross-env/issues/257)**
+
+---
+
+<!-- prettier-ignore-start -->
+[![Build Status][build-badge]][build]
+[![Code Coverage][coverage-badge]][coverage]
+[![version][version-badge]][package]
+[![downloads][downloads-badge]][npmtrends]
+[![MIT License][license-badge]][license]
+<!-- prettier-ignore-end -->
+
+## The problem
+
+Most Windows command prompts will choke when you set environment variables with
+`NODE_ENV=production` like that. (The exception is [Bash on Windows][win-bash],
+which uses native Bash.) Similarly, there's a difference in how windows and
+POSIX commands utilize environment variables. With POSIX, you use: `$ENV_VAR`
+and on windows you use `%ENV_VAR%`.
+
+## This solution
+
+`cross-env` makes it so you can have a single command without worrying about
+setting or using the environment variable properly for the platform. Just set it
+like you would if it's running on a POSIX system, and `cross-env` will take care
+of setting it properly.
+
+## Installation
+
+This module is distributed via [npm][npm] which is bundled with [node][node] and
+should be installed as one of your project's `devDependencies`:
+
+```
+npm install --save-dev cross-env
+```
+
+> WARNING! Make sure that when you're installing packages that you spell things
+> correctly to avoid [mistakenly installing malware][malware]
+
+> NOTE : Version 8 of cross-env only supports Node.js 20 and higher, to use it
+> on Node.js 18 or lower install version 7 `npm install --save-dev cross-env@7`
+
+## Usage
+
+I use this in my npm scripts:
+
+```json
+{
+	"scripts": {
+		"build": "cross-env NODE_ENV=production node ./start.js --enable-turbo-mode"
+	}
+}
+```
+
+Ultimately, the command that is executed (using [`cross-spawn`][cross-spawn])
+is:
+
+```
+node ./start.js --enable-turbo-mode
+```
+
+The `NODE_ENV` environment variable will be set by `cross-env`
+
+You can set multiple environment variables at a time:
+
+```json
+{
+	"scripts": {
+		"build": "cross-env FIRST_ENV=one SECOND_ENV=two node ./my-program"
+	}
+}
+```
+
+You can also split a command into several ones, or separate the environment
+variables declaration from the actual command execution. You can do it this way:
+
+```json
+{
+	"scripts": {
+		"parentScript": "cross-env GREET=\"Joe\" npm run childScript",
+		"childScript": "cross-env-shell \"echo Hello $GREET\""
+	}
+}
+```
+
+Where `childScript` holds the actual command to execute and `parentScript` sets
+the environment variables to use. Then instead of run the childScript you run
+the parent. This is quite useful for launching the same command with different
+env variables or when the environment variables are too long to have everything
+in one line. It also means that you can use `$GREET` env var syntax even on
+Windows which would usually require it to be `%GREET%`.
+
+If you precede a dollar sign with an odd number of backslashes the expression
+statement will not be replaced. Note that this means backslashes after the JSON
+string escaping took place. `"FOO=\\$BAR"` will not be replaced.
+`"FOO=\\\\$BAR"` will be replaced though.
+
+Lastly, if you want to pass a JSON string (e.g., when using [ts-loader]), you
+can do as follows:
+
+```json
+{
+	"scripts": {
+		"test": "cross-env TS_NODE_COMPILER_OPTIONS={\\\"module\\\":\\\"commonjs\\\"} node some_file.test.ts"
+	}
+}
+```
+
+Pay special attention to the **triple backslash** `(\\\)` **before** the
+**double quotes** `(")` and the **absence** of **single quotes** `(')`. Both of
+these conditions have to be met in order to work both on Windows and UNIX.
+
+## `cross-env` vs `cross-env-shell`
+
+The `cross-env` module exposes two bins: `cross-env` and `cross-env-shell`. The
+first one executes commands using [`cross-spawn`][cross-spawn], while the second
+one uses the `shell` option from Node's `spawn`.
+
+The main use case for `cross-env-shell` is when you need an environment variable
+to be set across an entire inline shell script, rather than just one command.
+
+For example, if you want to have the environment variable apply to several
+commands in series then you will need to wrap those in quotes and use
+`cross-env-shell` instead of `cross-env`.
+
+```json
+{
+	"scripts": {
+		"greet": "cross-env-shell GREETING=Hi NAME=Joe \"echo $GREETING && echo $NAME\""
+	}
+}
+```
+
+The rule of thumb is: if you want to pass to `cross-env` a command that contains
+special shell characters _that you want interpreted_, then use
+`cross-env-shell`. Otherwise stick to `cross-env`.
+
+On Windows you need to use `cross-env-shell`, if you want to handle
+[signal events](https://nodejs.org/api/process.html#process_signal_events)
+inside of your program. A common case for that is when you want to capture a
+`SIGINT` event invoked by pressing `Ctrl + C` on the command-line interface.
+
+## Windows Issues
+
+Please note that `npm` uses `cmd` by default and that doesn't support command
+substitution, so if you want to leverage that, then you need to update your
+`.npmrc` to set the `script-shell` to powershell.
+[Learn more here](https://github.com/kentcdodds/cross-env/issues/192#issuecomment-513341729).
+
+## Inspiration
+
+I originally created this to solve a problem I was having with my npm scripts in
+[angular-formly][angular-formly]. This made contributing to the project much
+easier for Windows users.
+
+## Other Solutions
+
+- [`env-cmd`](https://github.com/toddbluhm/env-cmd) - Reads environment
+  variables from a file instead
+- [`@naholyr/cross-env`](https://www.npmjs.com/package/@naholyr/cross-env) -
+  `cross-env` with support for setting default values
+
+## LICENSE
+
+MIT
+
+<!-- prettier-ignore-start -->
+[npm]: https://npmjs.com
+[node]: https://nodejs.org
+[build-badge]: https://img.shields.io/github/actions/workflow/status/kentcdodds/cross-env/validate.yml?branch=main&logo=github&style=flat-square
+[build]: https://github.com/kentcdodds/cross-env/actions?query=workflow%3Avalidate
+[coverage-badge]: https://img.shields.io/codecov/c/github/kentcdodds/cross-env.svg?style=flat-square
+[coverage]: https://codecov.io/github/kentcdodds/cross-env
+[version-badge]: https://img.shields.io/npm/v/cross-env.svg?style=flat-square
+[package]: https://www.npmjs.com/package/cross-env
+[downloads-badge]: https://img.shields.io/npm/dm/cross-env.svg?style=flat-square
+[npmtrends]: http://www.npmtrends.com/cross-env
+[license-badge]: https://img.shields.io/npm/l/cross-env.svg?style=flat-square
+[license]: https://github.com/kentcdodds/cross-env/blob/main/LICENSE
+
+[angular-formly]: https://github.com/formly-js/angular-formly
+[cross-spawn]: https://www.npmjs.com/package/cross-spawn
+[malware]: http://blog.npmjs.org/post/163723642530/crossenv-malware-on-the-npm-registry
+[ts-loader]: https://www.npmjs.com/package/ts-loader
+[win-bash]: https://msdn.microsoft.com/en-us/commandline/wsl/about
+<!-- prettier-ignore-end -->

backend/node_modules/cross-env/dist/bin/cross-env-shell.d.ts

@@ -0,0 +1,2 @@
+#!/usr/bin/env node
+export {};

backend/node_modules/cross-env/dist/bin/cross-env-shell.js

@@ -0,0 +1,3 @@
+#!/usr/bin/env node
+import { crossEnv } from "../index.js";
+crossEnv(process.argv.slice(2), { shell: true });

backend/node_modules/cross-env/dist/bin/cross-env.d.ts

@@ -0,0 +1,2 @@
+#!/usr/bin/env node
+export {};

backend/node_modules/cross-env/dist/bin/cross-env.js

@@ -0,0 +1,3 @@
+#!/usr/bin/env node
+import { crossEnv } from "../index.js";
+crossEnv(process.argv.slice(2));

backend/node_modules/cross-env/dist/command.d.ts

@@ -0,0 +1,8 @@
+/**
+ * Converts an environment variable usage to be appropriate for the current OS
+ * @param command Command to convert
+ * @param env Map of the current environment variable names and their values
+ * @param normalize If the command should be normalized using `path` after converting
+ * @returns Converted command
+ */
+export declare function commandConvert(command: string, env: NodeJS.ProcessEnv, normalize?: boolean): string;

backend/node_modules/cross-env/dist/command.js

@@ -0,0 +1,39 @@
+import path from 'path';
+import { isWindows } from "./is-windows.js";
+/**
+ * Converts an environment variable usage to be appropriate for the current OS
+ * @param command Command to convert
+ * @param env Map of the current environment variable names and their values
+ * @param normalize If the command should be normalized using `path` after converting
+ * @returns Converted command
+ */
+export function commandConvert(command, env, normalize = false) {
+    if (!isWindows()) {
+        return command;
+    }
+    // Handle simple variables: $var or ${var}
+    const simpleEnvRegex = /\$(\w+)|\${(\w+)}/g;
+    // Handle bash parameter expansion with default values: ${var:-default}
+    const defaultValueRegex = /\$\{(\w+):-([^}]+)\}/g;
+    let convertedCmd = command;
+    // First, handle bash parameter expansion with default values
+    convertedCmd = convertedCmd.replace(defaultValueRegex, (match, varName, defaultValue) => {
+        // If the variable exists, use its value; otherwise use the default
+        const value = env[varName] || defaultValue;
+        return value;
+    });
+    // Then handle simple variable references
+    convertedCmd = convertedCmd.replace(simpleEnvRegex, (match, $1, $2) => {
+        const varName = $1 || $2;
+        // In Windows, non-existent variables are not replaced by the shell,
+        // so for example "echo %FOO%" will literally print the string "%FOO%", as
+        // opposed to printing an empty string in UNIX. See kentcdodds/cross-env#145
+        // If the env variable isn't defined at runtime, just strip it from the command entirely
+        return env[varName] ? `%${varName}%` : '';
+    });
+    // Normalization is required for commands with relative paths
+    // For example, `./cmd.bat`. See kentcdodds/cross-env#127
+    // However, it should not be done for command arguments.
+    // See https://github.com/kentcdodds/cross-env/pull/130#issuecomment-319887970
+    return normalize === true ? path.normalize(convertedCmd) : convertedCmd;
+}

backend/node_modules/cross-env/dist/index.d.ts

@@ -0,0 +1,8 @@
+export type CrossEnvOptions = {
+    shell?: boolean;
+};
+export type ProcessResult = {
+    exitCode: number | null;
+    signal?: string | null;
+};
+export declare function crossEnv(args: string[], options?: CrossEnvOptions): ProcessResult | null;

backend/node_modules/cross-env/dist/index.js

@@ -0,0 +1,98 @@
+import { invariant } from '@epic-web/invariant';
+import { spawn } from 'cross-spawn';
+import { commandConvert } from "./command.js";
+import { varValueConvert } from "./variable.js";
+const envSetterRegex = /(\w+)=('(.*)'|"(.*)"|(.*))/;
+export function crossEnv(args, options = {}) {
+    const [envSetters, command, commandArgs] = parseCommand(args);
+    const env = getEnvVars(envSetters);
+    if (command) {
+        const spawnOptions = {
+            stdio: 'inherit',
+            shell: options.shell,
+            env,
+        };
+        const proc = spawn(
+        // run `path.normalize` for command(on windows)
+        commandConvert(command, env, true), 
+        // by default normalize is `false`, so not run for cmd args
+        commandArgs.map((arg) => commandConvert(arg, env)), spawnOptions);
+        process.on('SIGTERM', () => proc.kill('SIGTERM'));
+        process.on('SIGINT', () => proc.kill('SIGINT'));
+        process.on('SIGBREAK', () => proc.kill('SIGBREAK'));
+        process.on('SIGHUP', () => proc.kill('SIGHUP'));
+        proc.on('exit', (code, signal) => {
+            let crossEnvExitCode = code;
+            // exit code could be null when OS kills the process(out of memory, etc) or due to node handling it
+            // but if the signal is SIGINT the user exited the process so we want exit code 0
+            if (crossEnvExitCode === null) {
+                crossEnvExitCode = signal === 'SIGINT' ? 0 : 1;
+            }
+            process.exit(crossEnvExitCode);
+        });
+        return proc;
+    }
+    return null;
+}
+function parseCommand(args) {
+    const envSetters = {};
+    let command = null;
+    let commandArgs = [];
+    for (let i = 0; i < args.length; i++) {
+        const arg = args[i];
+        if (!arg)
+            continue;
+        const match = envSetterRegex.exec(arg);
+        if (match && match[1]) {
+            let value;
+            if (typeof match[3] !== 'undefined') {
+                value = match[3];
+            }
+            else if (typeof match[4] === 'undefined') {
+                value = match[5] || '';
+            }
+            else {
+                value = match[4];
+            }
+            envSetters[match[1]] = value;
+        }
+        else {
+            // No more env setters, the rest of the line must be the command and args
+            const cStart = args
+                .slice(i)
+                // Regex:
+                // match "\'" or "'"
+                // or match "\" if followed by [$"\] (lookahead)
+                .map((a) => {
+                const re = /\\\\|(\\)?'|([\\])(?=[$"\\])/g;
+                // Eliminate all matches except for "\'" => "'"
+                return a.replace(re, (m) => {
+                    if (m === '\\\\')
+                        return '\\';
+                    if (m === "\\'")
+                        return "'";
+                    return '';
+                });
+            });
+            const parsedCommand = cStart[0];
+            invariant(parsedCommand, 'Command is required');
+            command = parsedCommand;
+            commandArgs = cStart.slice(1).filter(Boolean);
+            break;
+        }
+    }
+    return [envSetters, command, commandArgs];
+}
+function getEnvVars(envSetters) {
+    const envVars = { ...process.env };
+    if (process.env.APPDATA) {
+        envVars.APPDATA = process.env.APPDATA;
+    }
+    Object.keys(envSetters).forEach((varName) => {
+        const value = envSetters[varName];
+        if (value !== undefined) {
+            envVars[varName] = varValueConvert(value, varName);
+        }
+    });
+    return envVars;
+}

backend/node_modules/cross-env/dist/is-windows.d.ts

@@ -0,0 +1,5 @@
+/**
+ * Determines if the current platform is Windows
+ * @returns true if running on Windows, false otherwise
+ */
+export declare function isWindows(): boolean;

backend/node_modules/cross-env/dist/is-windows.js

@@ -0,0 +1,8 @@
+/**
+ * Determines if the current platform is Windows
+ * @returns true if running on Windows, false otherwise
+ */
+export function isWindows() {
+    return (process.platform === 'win32' ||
+        /^(msys|cygwin)$/.test(process.env.OSTYPE || ''));
+}

backend/node_modules/cross-env/dist/variable.d.ts

@@ -0,0 +1,7 @@
+/**
+ * Converts an environment variable value to be appropriate for the current OS.
+ * @param originalValue Original value of the env variable
+ * @param originalName Original name of the env variable
+ * @returns Converted value
+ */
+export declare function varValueConvert(originalValue: string, originalName: string): string;

backend/node_modules/cross-env/dist/variable.js

@@ -0,0 +1,57 @@
+import { isWindows } from "./is-windows.js";
+const pathLikeEnvVarWhitelist = new Set(['PATH', 'NODE_PATH']);
+/**
+ * This will transform UNIX-style list values to Windows-style.
+ * For example, the value of the $PATH variable "/usr/bin:/usr/local/bin:."
+ * will become "/usr/bin;/usr/local/bin;." on Windows.
+ * @param varValue Original value of the env variable
+ * @param varName Original name of the env variable
+ * @returns Converted value
+ */
+function replaceListDelimiters(varValue, varName = '') {
+    const targetSeparator = isWindows() ? ';' : ':';
+    if (!pathLikeEnvVarWhitelist.has(varName)) {
+        return varValue;
+    }
+    return varValue.replace(/(\\*):/g, (match, backslashes) => {
+        if (backslashes.length % 2) {
+            // Odd number of backslashes preceding it means it's escaped,
+            // remove 1 backslash and return the rest as-is
+            return match.substring(1);
+        }
+        return backslashes + targetSeparator;
+    });
+}
+/**
+ * This will attempt to resolve the value of any env variables that are inside
+ * this string. For example, it will transform this:
+ * cross-env FOO=$NODE_ENV BAR=\\$NODE_ENV echo $FOO $BAR
+ * Into this:
+ * FOO=development BAR=$NODE_ENV echo $FOO
+ * (Or whatever value the variable NODE_ENV has)
+ * Note that this function is only called with the right-side portion of the
+ * env var assignment, so in that example, this function would transform
+ * the string "$NODE_ENV" into "development"
+ * @param varValue Original value of the env variable
+ * @returns Converted value
+ */
+function resolveEnvVars(varValue) {
+    const envUnixRegex = /(\\*)(\$(\w+)|\${(\w+)})/g; // $my_var or ${my_var} or \$my_var
+    return varValue.replace(envUnixRegex, (_, escapeChars, varNameWithDollarSign, varName, altVarName) => {
+        // do not replace things preceded by a odd number of \
+        if (escapeChars.length % 2 === 1) {
+            return varNameWithDollarSign;
+        }
+        return (escapeChars.substring(0, escapeChars.length / 2) +
+            (process.env[varName || altVarName] || ''));
+    });
+}
+/**
+ * Converts an environment variable value to be appropriate for the current OS.
+ * @param originalValue Original value of the env variable
+ * @param originalName Original name of the env variable
+ * @returns Converted value
+ */
+export function varValueConvert(originalValue, originalName) {
+    return resolveEnvVars(replaceListDelimiters(originalValue, originalName));
+}

backend/node_modules/cross-env/package.json

@@ -0,0 +1,89 @@
+{
+  "name": "cross-env",
+  "version": "10.1.0",
+  "description": "Run scripts that set and use environment variables across platforms",
+  "type": "module",
+  "main": "./dist/index.js",
+  "types": "./dist/index.d.ts",
+  "bin": {
+    "cross-env": "./dist/bin/cross-env.js",
+    "cross-env-shell": "./dist/bin/cross-env-shell.js"
+  },
+  "engines": {
+    "node": ">=20"
+  },
+  "scripts": {
+    "build": "zshy",
+    "dev": "zshy --watch",
+    "lint": "eslint .",
+    "lint:fix": "eslint . --fix",
+    "format": "prettier --write .",
+    "format:check": "prettier --check .",
+    "typecheck": "tsc --noEmit",
+    "test": "vitest",
+    "test:ui": "vitest --ui",
+    "test:run": "vitest run",
+    "test:coverage": "vitest run --coverage",
+    "test:e2e": "node e2e/test-cross-env.js && node e2e/test-cross-env-shell.js && node e2e/test-default-values.js",
+    "validate": "npm run build && npm run typecheck && npm run lint && npm run format:check && npm run test:run"
+  },
+  "files": [
+    "dist"
+  ],
+  "keywords": [
+    "cross-environment",
+    "environment variable",
+    "windows",
+    "cross-platform"
+  ],
+  "author": "Kent C. Dodds <me@kentcdodds.com> (https://kentcdodds.com)",
+  "license": "MIT",
+  "dependencies": {
+    "@epic-web/invariant": "^1.0.0",
+    "cross-spawn": "^7.0.6"
+  },
+  "devDependencies": {
+    "@epic-web/config": "^1.21.1",
+    "@types/cross-spawn": "^6.0.6",
+    "@types/node": "^24.1.0",
+    "@vitest/coverage-v8": "^3.2.4",
+    "@vitest/ui": "^3.2.4",
+    "eslint": "^9.32.0",
+    "prettier": "^3.6.2",
+    "typescript": "^5.8.3",
+    "vitest": "^3.2.4",
+    "zshy": "^0.3.0"
+  },
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/kentcdodds/cross-env.git"
+  },
+  "bugs": {
+    "url": "https://github.com/kentcdodds/cross-env/issues"
+  },
+  "homepage": "https://github.com/kentcdodds/cross-env#readme",
+  "zshy": {
+    "cjs": false,
+    "exports": {
+      ".": "./src/index.ts",
+      "./bin/cross-env": "./src/bin/cross-env.ts",
+      "./bin/cross-env-shell": "./src/bin/cross-env-shell.ts"
+    }
+  },
+  "prettier": "@epic-web/config/prettier",
+  "module": "./dist/index.js",
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "import": "./dist/index.js"
+    },
+    "./bin/cross-env": {
+      "types": "./dist/bin/cross-env.d.ts",
+      "import": "./dist/bin/cross-env.js"
+    },
+    "./bin/cross-env-shell": {
+      "types": "./dist/bin/cross-env-shell.d.ts",
+      "import": "./dist/bin/cross-env-shell.js"
+    }
+  }
+}