@cevek/screentest 0.2.5 → 0.3.1

package/dist/templates/Dockerfile.npm.tests

@@ -1,16 +0,0 @@
-FROM mcr.microsoft.com/playwright:v1.60.0-noble
-
-WORKDIR /work
-
-# Install dependencies. --ignore-scripts skips your project's postinstall
-# hooks (which usually scan src/ — not needed for the test image).
-COPY package.json package-lock.json ./
-RUN npm ci --ignore-scripts
-
-# tests/, vitest.screentest.config.ts, tsconfig.json, and snapshot.json are
-# bind-mounted by `screentest test` at run-time — no rebuild needed for test
-# or config edits. Rebuild only when package.json/package-lock.json change.
-
-# Run vitest directly (skipping `npm exec`) — keeps the test image simple
-# and matches how the host orchestrator invokes it.
-CMD ["./node_modules/.bin/vitest", "--config", "vitest.screentest.config.ts", "run"]

package/dist/templates/Dockerfile.pnpm.tests

@@ -1,27 +0,0 @@
-FROM mcr.microsoft.com/playwright:v1.60.0-noble
-
-WORKDIR /work
-
-# corepack lets us use whatever pnpm version your project's `packageManager`
-# field pins (pnpm 11 by default in modern projects). If your project uses
-# npm or yarn instead, swap the install commands accordingly.
-RUN corepack enable
-
-# Install dependencies. Flags:
-#   --ignore-scripts        skips your project's postinstall hooks (which
-#                            usually scan src/ — not needed for the test image).
-#   --config.minimumReleaseAge=0  bypass pnpm 11's supply-chain policy for
-#                            freshly-published packages (the test image is
-#                            ephemeral, runs only what's already in lockfile).
-COPY package.json pnpm-lock.yaml ./
-COPY pnpm-workspace.yaml* ./
-RUN pnpm install --frozen-lockfile --ignore-scripts --config.minimumReleaseAge=0
-
-# tests/, vitest.screentest.config.ts, tsconfig.json, and snapshot.json are
-# bind-mounted by `screentest test` at run-time — no rebuild needed for test
-# or config edits. Rebuild only when package.json/pnpm-lock.yaml change.
-
-# Run vitest directly (not via pnpm exec) — pnpm 11 re-runs its supply-chain
-# policy on every exec, which would re-fail freshly-published packages
-# even after install succeeded.
-CMD ["./node_modules/.bin/vitest", "--config", "vitest.screentest.config.ts", "run"]

package/dist/templates/Dockerfile.yarn.tests

@@ -1,20 +0,0 @@
-FROM mcr.microsoft.com/playwright:v1.60.0-noble
-
-WORKDIR /work
-
-# corepack lets yarn 2+/berry self-install from your project's
-# `packageManager` field. For yarn 1 it's a no-op (yarn is bundled in newer
-# Node images anyway).
-RUN corepack enable
-
-# Install dependencies. --ignore-scripts skips your project's postinstall
-# hooks (which usually scan src/ — not needed for the test image).
-COPY package.json yarn.lock ./
-COPY .yarnrc.yml* ./
-RUN yarn install --frozen-lockfile --ignore-scripts
-
-# tests/, vitest.screentest.config.ts, tsconfig.json, and snapshot.json are
-# bind-mounted by `screentest test` at run-time — no rebuild needed for test
-# or config edits. Rebuild only when package.json/yarn.lock change.
-
-CMD ["./node_modules/.bin/vitest", "--config", "vitest.screentest.config.ts", "run"]