diff --git a/.github/workflows/run-tests.yml b/.github/workflows/run-tests.yml index 123bc8e4..120a8125 100644 --- a/.github/workflows/run-tests.yml +++ b/.github/workflows/run-tests.yml @@ -71,4 +71,123 @@ jobs: cache-dependency-path: client/yarn.lock - run: yarn - run: yarn test + env: + # entities.test.js renders the full admin app ~140 times in one + # process (every resource's List/Create/Edit page); the default + # heap limit is tight enough on CI runners that later tests in the + # same run degrade/fail from GC pressure even though they pass + # fine in isolation. + NODE_OPTIONS: --max-old-space-size=4096 + + e2e-tests: + name: Run browser E2E tests + runs-on: ubuntu-latest + needs: prepare + if: ${{ needs.prepare.outputs.client == 'true' || needs.prepare.outputs.server == 'true' }} + services: + mysql: + image: mysql:8.4 + env: + MYSQL_ROOT_PASSWORD: root + MYSQL_DATABASE: mysql_database + ports: + - 3306:3306 + options: >- + --health-cmd="mysqladmin ping -proot" + --health-interval=10s + --health-timeout=5s + --health-retries=10 + env: + MYSQL_HOST: 127.0.0.1 + MYSQL_PORT: 3306 + MYSQL_USER: mysql_user + MYSQL_PASSWORD: mysql_password + MYSQL_DATABASE: mysql_database + JWT_SECRET: jwt_secret + steps: + - uses: actions/checkout@v4 + with: + submodules: recursive + - uses: actions/setup-node@v4 + with: + node-version: '20' + + # data.sql (the run-without-docker checkpoint dump) both creates the + # schema/seed data and grants mysql_user its privileges, but assumes + # the account itself already exists — the docker-based setup creates + # it via the image's own MYSQL_USER/MYSQL_PASSWORD env vars, which the + # plain `mysql:` service image doesn't expose the same way. + - name: Set up database + run: | + mysql -h127.0.0.1 -uroot -proot -e " + CREATE USER IF NOT EXISTS 'mysql_user'@'%' IDENTIFIED BY 'mysql_password'; + GRANT ALL PRIVILEGES ON mysql_database.* TO 'mysql_user'@'%'; + FLUSH PRIVILEGES; + " + mysql -h127.0.0.1 -uroot -proot mysql_database < db/data.sql + + - name: Install server deps, run pending migrations + working-directory: ./server + run: | + yarn + NODE_ENV=development yarn typeorm:run + + # Backgrounded within this step, with the wait loop right after it in + # the same step: the workflow can't move on to the next step until + # this one is confirmed answering requests — a later step starting + # before this one is truly ready would just fail on connection-refused + # instead of waiting for it. + - name: Start server + working-directory: ./server + run: | + NODE_ENV=development PORT=3001 yarn start:dev > /tmp/server.log 2>&1 & + ready=false + for i in $(seq 1 60); do + # Any HTTP response (even a 400 from an empty body) means the + # server is up; curl's own exit code only tells us the TCP + # connection was refused or not. GitHub Actions runs this script + # under `bash -e`, and `code=$(curl ...)` is a plain assignment + # (not exempt the way `curl ... && break` is) — so on the very + # first, expected-to-fail attempt curl's connection-refused exit + # code aborted the whole step before the retry loop ran at all. + # `|| true` neutralizes that; emptiness is still checked below. + code=$(curl -s -o /dev/null -w "%{http_code}" -X POST http://localhost:3001/auth/register -H "Content-Type: application/json" -d '{}' || true) + if [ -n "$code" ] && [ "$code" != "000" ]; then ready=true; break; fi + sleep 1 + done + if [ "$ready" != "true" ]; then + echo "Server did not become ready:"; cat /tmp/server.log; exit 1 + fi + + - name: Install client deps, start client + working-directory: ./client + run: | + yarn + yarn start > /tmp/client.log 2>&1 & + for i in $(seq 1 60); do + curl -sf -o /dev/null http://localhost:3000 && break + sleep 1 + done + curl -sf -o /dev/null http://localhost:3000 || (echo "Client did not become ready:"; cat /tmp/client.log; exit 1) + + - name: Install E2E deps + working-directory: ./e2e + run: | + yarn + # playwright.config.ts prefers a pre-installed Chromium at + # $PLAYWRIGHT_CHROMIUM_PATH (present in some dev sandboxes) but + # falls back to Playwright's own managed browser when that path + # doesn't exist — which is always the case on this runner. + npx playwright install --with-deps chromium + + - name: Run E2E tests + working-directory: ./e2e + run: yarn test + + - uses: actions/upload-artifact@v4 + if: failure() + with: + name: playwright-report + path: e2e/test-results/ + retention-days: 7 diff --git a/client/shared b/client/shared index fa2feeb8..a8c10e8d 160000 --- a/client/shared +++ b/client/shared @@ -1 +1 @@ -Subproject commit fa2feeb8f7d0dfe44d073d0d308940f5821b341c +Subproject commit a8c10e8de5149397cd0a5bbb1246d181d7796c26 diff --git a/e2e/.gitignore b/e2e/.gitignore new file mode 100644 index 00000000..dbd64df8 --- /dev/null +++ b/e2e/.gitignore @@ -0,0 +1,3 @@ +node_modules/ +test-results/ +playwright-report/ diff --git a/e2e/README.md b/e2e/README.md new file mode 100644 index 00000000..55bc11e2 --- /dev/null +++ b/e2e/README.md @@ -0,0 +1,112 @@ +# Browser E2E (Playwright) + +Real-browser tests, driving the actual client + server + a real database — not +mocks, not jsdom. Deliberately narrow: three flows chosen for what only a real +browser + server + database can catch, not for breadth (the jsdom-based +`entities.test.js` smoke tests already cover every resource page cheaply — +see "What this catches that jsdom smoke tests don't" below). Wired into CI +as the `e2e-tests` job in `.github/workflows/run-tests.yml`, which stands up +a real MySQL service container, runs migrations, boots server + client, then +runs this suite against them. + +## Why Playwright, and which browser it launches + +Some dev sandboxes this pilot runs in ship a pre-installed Chromium under +`$PLAYWRIGHT_BROWSERS_PATH` (`/opt/pw-browsers`), so there's no download step +there — `playwright.config.ts` points `launchOptions.executablePath` at +`/opt/pw-browsers/chromium` (a stable symlink to the current versioned +build) when that path exists, which avoids both a network fetch that may +not be reachable in a sandbox and a redundant download of a browser that's +already there. Override with `PLAYWRIGHT_CHROMIUM_PATH` if your environment +installs it elsewhere. + +CI (and most other environments) doesn't have that path — there, +`executablePath` is left unset and Playwright falls back to its own managed +browser, installed by the `Install E2E deps` step's `npx playwright install +--with-deps chromium`. Run that same command locally first if your +environment has neither a pre-installed Chromium nor one Playwright has +already downloaded. + +## Prerequisites: a live stack + +Playwright needs the client and server actually running against a real +database — see the `run-without-docker` skill (`multi-repo-codespace/.github/skills/`) +for the full walkthrough if you don't have Docker. Short version: + +```bash +# 1. MySQL, once +apt-get install -y mysql-server-8.0 && service mysql start +mysql -u root -e " + CREATE DATABASE mysql_database CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci; + CREATE USER 'mysql_user'@'localhost' IDENTIFIED BY 'mysql_password'; + GRANT ALL PRIVILEGES ON mysql_database.* TO 'mysql_user'@'localhost'; + GRANT SYSTEM_USER ON *.* TO 'mysql_user'@'localhost'; + FLUSH PRIVILEGES; +" + +# 2. Load the schema checkpoint + remaining migrations (fast path — see +# run-without-docker for the full-replay alternative) +mysql -u root mysql_database < db/data.sql +cd server && NODE_ENV=development yarn typeorm:run + +# 3. Start server and client — NODE_ENV=development is required, not optional: +# server/shared/utils/bootstrap.util.ts only allows the browser's +# localhost origin through CORS when NODE_ENV === 'development'. Without +# it every request from the client to the API fails as a silent CORS +# error in the browser (curl/supertest calls don't hit this — they don't +# send an Origin header — so this is easy to miss when smoke-testing the +# API directly). +NODE_ENV=development MYSQL_HOST=localhost MYSQL_PORT=3306 \ + MYSQL_USER=mysql_user MYSQL_PASSWORD=mysql_password MYSQL_DATABASE=mysql_database \ + JWT_SECRET=jwt_secret PORT=3001 yarn start:dev # server, separate shell + +cd client && yarn start # client, separate shell — picks 3000, falls back if taken +``` + +Default API URL resolution in the client (`constantsProvider.js`) is +`http://:`, so client on 3000 + server on 3001 +just works with no extra client-side config. + +## Running + +```bash +cd e2e +yarn install +yarn test # against http://localhost:3000 +E2E_BASE_URL=... E2E_API_URL=... yarn test # against a different stack +``` + +## What's covered + +All three specs share `tests/helpers.ts`'s `registerTestUser()` — registers a +fresh user via the API (same pattern as `server/test/*-crud.e2e-spec.ts`, not +seeded DB fixtures — the checkpoint dump's password hashes aren't real bcrypt +hashes of any known password) — and `loginThroughUi()`, which logs that user +in through the actual UI form. + +- `tests/login-dashboard.spec.ts` — confirms the dashboard loads after login + (sidebar renders, no leftover login form, no error page). +- `tests/crud-roundtrip.spec.ts` — creates, edits, and deletes a `klass_type` + through the real UI, checking after each step that the change actually + round-tripped through the server and database (not just that the request + didn't throw). `klass_type` is used because, as a non-admin user, it only + needs two plain fields (no reference-picker dropdown to drive). +- `tests/export-download.spec.ts` — downloads a real Excel export and checks + the file is non-empty. Exporting is gated on the user's `isPaid` flag, which + nothing in the app itself can set for a fresh registration, so + `tests/helpers.ts`'s `markUserAsPaid()` reaches directly into the database — + setup for the flow under test, same reasoning as `registerTestUser()` + reaching around the UI via the API. + +## What this catches that jsdom smoke tests don't + +Real browser rendering, real CORS/cookie/auth wiring end to end, an actual +multi-page flow (form submit → redirect → authenticated data fetch → +render), a create/edit/delete that really persists through the server and +database instead of a mocked `dataProvider`, and a real server-generated +file (the export test) — none of which a jsdom test with a mocked +`dataProvider` can exercise, since there's no real server or file on the +other end of the call. `entities.test.js`'s smoke tests are cheaper and +catch a different, much larger class of bug (any resource crashing on +mount) across every resource in the app — see that file's comments for the +trade-off between the two. diff --git a/e2e/package.json b/e2e/package.json new file mode 100644 index 00000000..5aea6f57 --- /dev/null +++ b/e2e/package.json @@ -0,0 +1,11 @@ +{ + "name": "react-admin-nestjs-e2e", + "private": true, + "scripts": { + "test": "playwright test" + }, + "devDependencies": { + "@playwright/test": "^1.48.0", + "mysql2": "^3.11.0" + } +} diff --git a/e2e/playwright.config.ts b/e2e/playwright.config.ts new file mode 100644 index 00000000..45fdf8d0 --- /dev/null +++ b/e2e/playwright.config.ts @@ -0,0 +1,27 @@ +import { defineConfig } from '@playwright/test'; +import { existsSync } from 'fs'; + +// The sandboxed dev environment this pilot was first built in ships a +// pre-installed Chromium under $PLAYWRIGHT_BROWSERS_PATH (/opt/pw-browsers) +// with a stable `chromium` symlink to the current versioned build — using +// it avoids a redundant download there. GitHub Actions runners (and most +// other environments) don't have that path at all, so this only pins +// executablePath when the path is actually present; otherwise it's left +// undefined and Playwright falls back to its own managed browser (installed +// via `npx playwright install --with-deps chromium` — see the CI workflow +// and this package's README). +const sandboxChromium = process.env.PLAYWRIGHT_CHROMIUM_PATH || '/opt/pw-browsers/chromium'; + +export default defineConfig({ + testDir: './tests', + timeout: 30000, + retries: 0, + use: { + baseURL: process.env.E2E_BASE_URL || 'http://localhost:3000', + launchOptions: { + ...(existsSync(sandboxChromium) ? { executablePath: sandboxChromium } : {}), + args: ['--no-sandbox'], + }, + screenshot: 'only-on-failure', + }, +}); diff --git a/e2e/tests/crud-roundtrip.spec.ts b/e2e/tests/crud-roundtrip.spec.ts new file mode 100644 index 00000000..7bcbc721 --- /dev/null +++ b/e2e/tests/crud-roundtrip.spec.ts @@ -0,0 +1,54 @@ +import { test, expect } from '@playwright/test'; +import { registerTestUser, loginThroughUi } from './helpers'; + +// Exercises a real dataProvider <-> nestjs-crud round trip through the +// actual UI: create, appears in the list, edit, change is visible, delete, +// gone from the list. jsdom's entities.test.js smoke tests (mocked +// dataProvider) prove pages don't crash on mount; they can't prove a create +// actually persists, an edit actually updates, or a delete actually removes +// a row — that needs a real server and a real database. +// +// klass_type is used because as a non-admin user (a fresh registration, +// same as the login test) it only requires two fields — key (number) and +// name (text) — with no reference picker to drive; every other field on +// this app's entities that was checked either needed a reference-select +// dropdown or is admin-only. +test('create, edit and delete a klass type through the real UI and API', async ({ page }) => { + const { username, password } = await registerTestUser(); + await loginThroughUi(page, username, password); + + const uniqueSuffix = Date.now(); + const originalName = `E2E Klass ${uniqueSuffix}`; + const updatedName = `E2E Klass ${uniqueSuffix} (updated)`; + + // --- Create --- + await page.goto('/klass_type/create'); + await page.locator('input[name="key"]').fill('1'); + await page.locator('input[name="name"]').fill(originalName); + await page.locator('button[type="submit"]').first().click(); + + // A successful create redirects to the list, which is the read half of + // the round trip: the row has to come back from a real GET, not just be + // assumed present because the POST returned 2xx. + await expect(page).toHaveURL(/\/klass_type$/, { timeout: 10000 }); + await expect(page.getByText(originalName, { exact: true })).toBeVisible({ timeout: 10000 }); + + // --- Edit --- + await page.getByText(originalName, { exact: true }).click(); + await expect(page).toHaveURL(/\/klass_type\/\d+$/, { timeout: 10000 }); + const nameInput = page.locator('input[name="name"]'); + await nameInput.fill(updatedName); + await page.locator('button[type="submit"]').first().click(); + + await expect(page).toHaveURL(/\/klass_type$/, { timeout: 10000 }); + await expect(page.getByText(updatedName, { exact: true })).toBeVisible({ timeout: 10000 }); + // The pre-edit name should be gone, not just the new one added alongside it. + await expect(page.getByText(originalName, { exact: true })).toHaveCount(0); + + // --- Delete --- + await page.locator('input[type="checkbox"]').nth(1).check(); + await page.getByRole('button', { name: 'מחק' }).click(); + await page.getByRole('button', { name: 'אשר' }).click(); + + await expect(page.getByText(updatedName, { exact: true })).toHaveCount(0, { timeout: 10000 }); +}); diff --git a/e2e/tests/export-download.spec.ts b/e2e/tests/export-download.spec.ts new file mode 100644 index 00000000..af2ba08a --- /dev/null +++ b/e2e/tests/export-download.spec.ts @@ -0,0 +1,48 @@ +import { test, expect } from '@playwright/test'; +import fs from 'fs'; +import { registerTestUser, loginThroughUi, markUserAsPaid } from './helpers'; + +// Downloads a real Excel export of a real list. jsdom cannot exercise this +// at all: the server builds actual .xlsx bytes (see server/shared's +// BaseReportGenerator family) and the client turns a base64 JSON payload +// into a real browser download via file-saver — there is no DOM to render, +// so a mocked-dataProvider unit test has nothing to assert against here. +// This is the file-download counterpart to crud-roundtrip's persistence +// check: it proves the export pipeline produces real, non-empty content, +// not just that clicking the button doesn't throw. +test('exports a real, non-empty Excel file for a resource', async ({ page }) => { + const { username, password } = await registerTestUser(); + + // Exporting is gated on the user's isPaid flag (see server/shared's + // base-entity.util validateUserHasPaid). There is no self-service way to + // become paid through the app itself — billing happens outside it — so + // this reaches directly into the DB, same as registerTestUser reaches + // around the UI via the API: setup for the flow under test, not the flow + // itself. + await markUserAsPaid(username); + + await loginThroughUi(page, username, password); + + // The export button is disabled when the list is empty, so give it one + // row to actually export. + await page.goto('/klass_type/create'); + await page.locator('input[name="key"]').fill('1'); + await page.locator('input[name="name"]').fill(`Export Test ${Date.now()}`); + await page.locator('button[type="submit"]').first().click(); + await expect(page).toHaveURL(/\/klass_type$/, { timeout: 10000 }); + + await page.getByRole('button', { name: 'ייצא' }).click(); + + const downloadPromise = page.waitForEvent('download', { timeout: 10000 }); + await page.getByRole('menuitem', { name: 'אקסל' }).click(); + const download = await downloadPromise; + + expect(download.suggestedFilename()).toMatch(/\.xlsx$/); + + const path = await download.path(); + expect(path).toBeTruthy(); + const { size } = fs.statSync(path!); + // A real xlsx (it's a zip container) is at minimum a few hundred bytes; + // an empty/corrupt response would be at or near 0. + expect(size).toBeGreaterThan(200); +}); diff --git a/e2e/tests/helpers.ts b/e2e/tests/helpers.ts new file mode 100644 index 00000000..5463cdb9 --- /dev/null +++ b/e2e/tests/helpers.ts @@ -0,0 +1,69 @@ +import { request } from '@playwright/test'; +import mysql from 'mysql2/promise'; + +const API_BASE_URL = process.env.E2E_API_URL || 'http://localhost:3001'; + +/** + * Registers a fresh test user directly against the API (same endpoint and + * pattern already proven in server/test/*.e2e-spec.ts) rather than relying on + * seeded DB fixtures, whose password hashes aren't real bcrypt hashes of any + * known password. + */ +export async function registerTestUser() { + const apiContext = await request.newContext(); + try { + const username = `pw_e2e_user_${Date.now()}_${Math.floor(Math.random() * 1000)}`; + const password = 'TestPass_123'; + const res = await apiContext.post(`${API_BASE_URL}/auth/register`, { + data: { username, password, name: 'Playwright E2E' }, + }); + if (!res.ok()) { + throw new Error(`Failed to register test user: ${res.status()} ${await res.text()}`); + } + return { username, password }; + } finally { + await apiContext.dispose(); + } +} + +/** + * Flips a freshly-registered user's `isPaid` flag directly in the database. + * + * There is no self-service "pay" flow in this app (billing happens outside + * it), and the one endpoint that can set isPaid (`/user` bulkUpdatePaid) + * requires the `showUsersData` permission a fresh registration never has. + * Some actions — exporting a resource, for one — are gated on isPaid, so a + * test that needs one of those has no way to arrange that state through the + * app itself. Reaching directly into the DB here mirrors registerTestUser's + * own reasoning: this is setup for the flow under test, not the flow itself. + * + * Uses the same MYSQL_* env vars (and same local defaults) as the server's + * own .env — see the e2e README's "Prerequisites" section. + */ +export async function markUserAsPaid(username: string) { + const connection = await mysql.createConnection({ + host: process.env.MYSQL_HOST || 'localhost', + port: Number(process.env.MYSQL_PORT) || 3306, + user: process.env.MYSQL_USER || 'mysql_user', + password: process.env.MYSQL_PASSWORD || 'mysql_password', + database: process.env.MYSQL_DATABASE || 'mysql_database', + }); + try { + const [result] = await connection.execute('UPDATE users SET isPaid = 1 WHERE email = ?', [username]); + // @ts-expect-error mysql2's OkPacket typing doesn't surface affectedRows on the union type + if (result.affectedRows !== 1) { + throw new Error(`Expected to mark exactly 1 user as paid, affected ${result.affectedRows}`); + } + } finally { + await connection.end(); + } +} + +/** Logs a registered user in through the actual UI form, from /login. */ +export async function loginThroughUi(page, username: string, password: string) { + await page.goto('/login'); + await page.locator('input[name="username"]').fill(username); + await page.locator('input[name="password"]').fill(password); + await page.getByRole('button', { name: /login|sign in|התחבר|כניסה/i }).click(); + await page.getByRole('menuitem').first().waitFor({ state: 'visible', timeout: 15000 }); +} diff --git a/e2e/tests/login-dashboard.spec.ts b/e2e/tests/login-dashboard.spec.ts new file mode 100644 index 00000000..b1ef1c40 --- /dev/null +++ b/e2e/tests/login-dashboard.spec.ts @@ -0,0 +1,24 @@ +import { test, expect } from '@playwright/test'; +import { registerTestUser } from './helpers'; + +test('login redirects to a working dashboard', async ({ page }) => { + const { username, password } = await registerTestUser(); + + await page.goto('/login'); + + // react-admin's default LoginForm renders TextInputs with source="username"/"password" + await page.locator('input[name="username"]').fill(username); + await page.locator('input[name="password"]').fill(password); + await page.getByRole('button', { name: /login|sign in|התחבר|כניסה/i }).click(); + + // Successful login redirects off the login page into the admin shell. + // The sidebar menu (role=menuitem) only renders once auth + permissions + // resolve and the layout mounts without crashing. + const menuItems = page.getByRole('menuitem'); + await expect(menuItems.first()).toBeVisible({ timeout: 15000 }); + await expect(menuItems).not.toHaveCount(0); + + // No leftover login form, and no error page reached instead of the dashboard. + await expect(page.locator('input[name="password"]')).toHaveCount(0); + await expect(page.getByText(/something went wrong/i)).toHaveCount(0); +}); diff --git a/e2e/yarn.lock b/e2e/yarn.lock new file mode 100644 index 00000000..a292a18d --- /dev/null +++ b/e2e/yarn.lock @@ -0,0 +1,93 @@ +# THIS IS AN AUTOGENERATED FILE. DO NOT EDIT THIS FILE DIRECTLY. +# yarn lockfile v1 + + +"@playwright/test@^1.48.0": + version "1.62.1" + resolved "https://registry.npmjs.org/@playwright/test/-/test-1.62.1.tgz#68e1aaf6e480e1923936dee6c66fae1921d3a65a" + integrity sha512-DTcUc8qii+cpHvtOwggMtBRMjKZHXYWdw8syRYu2vtzuq4Wxphqq4NfCs5Zt44L6mA8rfDfj+PHnxFc/FeK6mQ== + dependencies: + playwright "1.62.1" + +aws-ssl-profiles@^1.1.2: + version "1.1.2" + resolved "https://registry.npmjs.org/aws-ssl-profiles/-/aws-ssl-profiles-1.1.2.tgz#157dd77e9f19b1d123678e93f120e6f193022641" + integrity sha512-NZKeq9AfyQvEeNlN0zSYAaWrmBffJh3IELMZfRpJVWgrpEbtEpnjvzqBPf+mxoI287JohRDoa+/nsfqqiZmF6g== + +fsevents@2.3.2: + version "2.3.2" + resolved "https://registry.npmjs.org/fsevents/-/fsevents-2.3.2.tgz#8a526f78b8fdf4623b709e0b975c52c24c02fd1a" + integrity sha512-xiqMQR4xAeHTuB9uWm+fFRcIOgKBMiOBP+eXiyT7jsgVCq1bkVygt00oASowB7EdtpOHaaPgKt812P9ab+DDKA== + +generate-function@^2.3.1: + version "2.3.1" + resolved "https://registry.npmjs.org/generate-function/-/generate-function-2.3.1.tgz#f069617690c10c868e73b8465746764f97c3479f" + integrity sha512-eeB5GfMNeevm/GRYq20ShmsaGcmI81kIX2K9XQx5miC8KdHaC6Jm0qQ8ZNeGOi7wYB8OsdxKs+Y2oVuTFuVwKQ== + dependencies: + is-property "^1.0.2" + +iconv-lite@^0.7.3: + version "0.7.3" + resolved "https://registry.npmjs.org/iconv-lite/-/iconv-lite-0.7.3.tgz#84ee12f963e7de50bc01a13e160a078b3b0f415f" + integrity sha512-IKXpvIzjnC9XTAUbVBcMfGS0EPaIXtW6v+zr+RRp+hqULEpo0owZax6wyRwPOJbWbzjYspQwusTsfVr0ifh4uQ== + dependencies: + safer-buffer ">= 2.1.2 < 3.0.0" + +is-property@^1.0.2: + version "1.0.2" + resolved "https://registry.npmjs.org/is-property/-/is-property-1.0.2.tgz#57fe1c4e48474edd65b09911f26b1cd4095dda84" + integrity sha512-Ks/IoX00TtClbGQr4TWXemAnktAQvYB7HzcCxDGqEZU6oCmb2INHuOoKxbtR+HFkmYWBKv/dOZtGRiAjDhj92g== + +long@^5.3.2: + version "5.3.2" + resolved "https://registry.npmjs.org/long/-/long-5.3.2.tgz#1d84463095999262d7d7b7f8bfd4a8cc55167f83" + integrity sha512-mNAgZ1GmyNhD7AuqnTG3/VQ26o760+ZYBPKjPvugO8+nLbYfX6TVpJPseBvopbdY+qpZ/lKUnmEc1LeZYS3QAA== + +lru.min@^1.1.0, lru.min@^1.1.4: + version "1.1.4" + resolved "https://registry.npmjs.org/lru.min/-/lru.min-1.1.4.tgz#6ea1737a8c1ba2300cc87ad46910a4bdffa0117b" + integrity sha512-DqC6n3QQ77zdFpCMASA1a3Jlb64Hv2N2DciFGkO/4L9+q/IpIAuRlKOvCXabtRW6cQf8usbmM6BE/TOPysCdIA== + +mysql2@^3.11.0: + version "3.23.3" + resolved "https://registry.npmjs.org/mysql2/-/mysql2-3.23.3.tgz#85247f36f35bd180d3ba18b1f60fa7d553960ee2" + integrity sha512-ehp9HEKr4wVJaBOUVxNFa+CNrsCCCZ6363/jbGhb7WpEmSRNIXjHBjFs5K2s2cXn7j/RhDieejsQJ6nfUwD6vQ== + dependencies: + aws-ssl-profiles "^1.1.2" + generate-function "^2.3.1" + iconv-lite "^0.7.3" + long "^5.3.2" + lru.min "^1.1.4" + named-placeholders "^1.1.6" + sql-escaper "^1.5.1" + +named-placeholders@^1.1.6: + version "1.1.6" + resolved "https://registry.npmjs.org/named-placeholders/-/named-placeholders-1.1.6.tgz#c50c6920b43f258f59c16add1e56654f5cc02bb5" + integrity sha512-Tz09sEL2EEuv5fFowm419c1+a/jSMiBjI9gHxVLrVdbUkkNUUfjsVYs9pVZu5oCon/kmRh9TfLEObFtkVxmY0w== + dependencies: + lru.min "^1.1.0" + +playwright-core@1.62.1: + version "1.62.1" + resolved "https://registry.npmjs.org/playwright-core/-/playwright-core-1.62.1.tgz#120f67a19181bfd183c60fa903c0d99330b56785" + integrity sha512-wPYSwEBJY9GHraISXqyqtx0na0LpO3XEX7jNDhntbex7tzUS7kLnZsOlFruFJB4Hi/rhDMjXGqHewDZ68nYZVw== + +playwright@1.62.1: + version "1.62.1" + resolved "https://registry.npmjs.org/playwright/-/playwright-1.62.1.tgz#8447b6755e8aec85a3cb7207c823e3ed2fc66700" + integrity sha512-0M+L3LAD8/nm554LOla9Ayx0j0tmFZ0FBcoQ7F1VuVHpM/XpiC8RcDzBQB8W5+hA8L22THxELzeF+2WcUzvcLg== + dependencies: + playwright-core "1.62.1" + optionalDependencies: + fsevents "2.3.2" + +"safer-buffer@>= 2.1.2 < 3.0.0": + version "2.1.2" + resolved "https://registry.npmjs.org/safer-buffer/-/safer-buffer-2.1.2.tgz#44fa161b0187b9549dd84bb91802f9bd8385cd6a" + integrity sha512-YZo3K82SD7Riyi0E1EQPojLz7kpepnSQI9IyPbHHg1XXXevb5dJI7tpyN2ADxGcQbHG7vcyRHk0cbwqcQriUtg== + +sql-escaper@^1.5.1: + version "1.5.1" + resolved "https://registry.npmjs.org/sql-escaper/-/sql-escaper-1.5.1.tgz#fbaee511294d1f7da92fb68ca1faee2255839c7b" + integrity sha512-4toX5E1fQbBrpfXidaHnF0669nkAdETeIPTs2SUjxxD7RRIs9ICG4gtpmfc68JCEKehsdwLFqBu9VlQqZ1P1gg==