Clarify Vercel production-readiness audit scope: web-app vs API/CLI by Copilot · Pull Request #60 · Krosebrook/interact

Copilot · 2026-02-21T01:56:04Z

The PRD generator applied the same Vercel deployment section to every project type, even APIs and CLIs that cannot be deployed to Vercel. This adds explicit project-type awareness so the generated report either includes a full Vercel checklist or marks it N/A accordingly.

Changes

`scripts/generate-prd.js`

--project-type / -t flag — accepts web-app (default), api, or cli
generateVercelSection(projectType) helper — isolates the conditional logic from the template string
§12.5 Vercel Production-Readiness — new section in the deployment chapter:
- web-app: 9-item checklist (vercel.json config, env vars, security headers, SPA rewrites, edge regions, build validation, secret hygiene)
- api / cli: N/A notice with explanation and redirect to appropriate runtimes
Interactive mode now prompts for project type; non-interactive mode merges the flag into context

`src/test/generate-prd.test.js`

5 new tests covering: web-app checklist presence, api N/A, cli N/A, default-to-web-app, and api/cli message differentiation

Example

# Web app — full Vercel checklist in §12.5
node scripts/generate-prd.js --idea "Add dark mode" --project-type web-app

# Backend function — §12.5 marked N/A
node scripts/generate-prd.js --idea "New aggregation endpoint" --project-type api

api output for §12.5:

N/A — This is a backend API project and is not applicable for Vercel web deployment. Vercel hosts web apps (e.g., Next.js, Vite); API projects should be deployed to their own appropriate runtime (e.g., Base44 serverless functions, Docker, cloud run).

Original prompt

Clarify scope for Vercel production-readiness audit: determine whether to evaluate only web apps (Next.js/Vite/etc.) or also include APIs/CLIs and mark them as not applicable for Vercel. Update audit/report generation accordingly.

This pull request was created from Copilot chat.

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

Summary by cubic

Clarifies the Vercel production-readiness audit to focus on web apps and mark APIs/CLIs as not applicable in PRD reports. Adds a project type flag and interactive prompt to control scope.

New Features
- Adds --project-type (-t) flag (web-app | api | cli) and interactive prompt to set project type.
- Generates Vercel section (§12.5): full checklist for web apps; “N/A for Vercel” note with reason for API/CLI.
- Updates report output to show clear N/A without failing the audit.
Migration
- Use --project-type or answer the prompt (default: web-app).
- Re-run the generator to produce updated reports.

^{Written for commit e8eef13. Summary will update on new commits.}

Co-authored-by: Krosebrook <214532761+Krosebrook@users.noreply.github.com>

Copilot

Pull request overview

This PR adds project-type awareness to the PRD generator script, enabling it to conditionally generate Vercel production-readiness checklists based on whether the project is a web application, API, or CLI tool. This addresses the problem where the generator was inappropriately including Vercel deployment checklists for non-web projects that cannot be deployed to Vercel.

Changes:

Added --project-type / -t CLI flag and interactive prompt accepting web-app, api, or cli values
Introduced generateVercelSection() helper function that returns either a full Vercel checklist or N/A message based on project type
Added comprehensive test coverage for the new project-type functionality with 5 test cases

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 5 comments.

File	Description
`scripts/generate-prd.js`	Added project-type CLI flag, interactive prompt, and conditional Vercel section generation logic
`src/test/generate-prd.test.js`	Added test suite covering web-app checklist, api/cli N/A messages, default behavior, and message differentiation
`package-lock.json`	Peer dependency marker updates (unrelated to PR's main functionality)

Copilot · 2026-02-21T22:15:07Z

src/test/generate-prd.test.js

+    // Inline implementation of generateVercelSection for isolated unit tests
+    function generateVercelSection(projectType) {
+      const isNonWebApp = projectType === 'api' || projectType === 'cli';
+      if (isNonWebApp) {
+        const kind = projectType === 'api' ? 'backend API' : 'CLI';
+        return `> **N/A** \u2014 This is a ${kind} project and is not applicable for Vercel web deployment. Vercel hosts web apps (e.g., Next.js, Vite); ${projectType === 'api' ? 'API' : 'CLI'} projects should be deployed to their own appropriate runtime (e.g., Base44 serverless functions, Docker, cloud run).`;
+      }
+      return [
+        '- [ ] `vercel.json` present and configured (framework, buildCommand, outputDirectory)',
+        '- [ ] Environment variables defined in Vercel dashboard (not hard-coded)',
+        '- [ ] Preview deployments enabled for pull requests',
+        '- [ ] Production domain configured with valid SSL certificate',
+        '- [ ] Security headers set (X-Content-Type-Options, X-Frame-Options, Referrer-Policy)',
+        '- [ ] `rewrites` / `redirects` configured for SPA routing (e.g., `/api/:path*`)',
+        '- [ ] Edge network region(s) selected appropriate for target audience',
+        '- [ ] Build passes locally with `npm run build` (output to `dist/` or configured `outputDirectory`)',
+        '- [ ] No secrets committed to source; all sensitive values use Vercel environment variable references',
+      ].join('\n');
+    }


The test suite duplicates the entire generateVercelSection function (lines 298-315) instead of importing it from the source. This creates a maintainability issue: if the actual implementation in scripts/generate-prd.js changes, the test copy must be manually kept in sync, risking test drift.

Consider exporting generateVercelSection from scripts/generate-prd.js so tests can import and test the actual implementation, or add a comment explaining why the duplication is intentional (e.g., for isolated unit testing without module dependencies).

Copilot · 2026-02-21T22:15:07Z

src/test/generate-prd.test.js

+    it('should default to web-app when projectType is not set', () => {
+      const section = generateVercelSection('web-app');
+
+      expect(section).toContain('vercel.json');
+      expect(section).not.toContain('N/A');
+    });


The test "should default to web-app when projectType is not set" doesn't actually test the default behavior. It explicitly passes 'web-app' to the function instead of testing what happens when projectType is undefined or an invalid value.

To properly test the default behavior, pass undefined, null, or an unrecognized value and verify it defaults to the web-app checklist.

Copilot · 2026-02-21T22:15:07Z

scripts/generate-prd.js

+  const isNonWebApp = projectType === 'api' || projectType === 'cli';
+  if (isNonWebApp) {
+    const kind = projectType === 'api' ? 'backend API' : 'CLI';
+    return `> **N/A** \u2014 This is a ${kind} project and is not applicable for Vercel web deployment. Vercel hosts web apps (e.g., Next.js, Vite); ${projectType === 'api' ? 'API' : 'CLI'} projects should be deployed to their own appropriate runtime (e.g., Base44 serverless functions, Docker, cloud run).`;


The function is case-sensitive and doesn't handle common variations. For example, 'API' (uppercase), 'Web-App' (capitalized), or 'CLI' (uppercase) would all be treated as web-app. This could be confusing for users.

Consider normalizing the input by converting to lowercase before comparison, or accept common case variations explicitly.

Suggested change

const isNonWebApp = projectType === 'api' || projectType === 'cli';

if (isNonWebApp) {

const kind = projectType === 'api' ? 'backend API' : 'CLI';

return `> **N/A** \u2014 This is a ${kind} project and is not applicable for Vercel web deployment. Vercel hosts web apps (e.g., Next.js, Vite); ${projectType === 'api' ? 'API' : 'CLI'} projects should be deployed to their own appropriate runtime (e.g., Base44 serverless functions, Docker, cloud run).`;

const normalizedType = (projectType || '').toString().trim().toLowerCase();

const isNonWebApp = normalizedType === 'api' || normalizedType === 'cli';

if (isNonWebApp) {

const kind = normalizedType === 'api' ? 'backend API' : 'CLI';

const label = normalizedType === 'api' ? 'API' : 'CLI';

return `> **N/A** \u2014 This is a ${kind} project and is not applicable for Vercel web deployment. Vercel hosts web apps (e.g., Next.js, Vite); ${label} projects should be deployed to their own appropriate runtime (e.g., Base44 serverless functions, Docker, cloud run).`;

Copilot · 2026-02-21T22:15:08Z

scripts/generate-prd.js

+      case '--project-type':
+      case '-t':
+        options.projectType = next;
+        i++;
+        break;


Missing input validation for project type. The code accepts any string value for --project-type but only handles 'web-app', 'api', and 'cli'. Invalid values (e.g., 'webapp', 'backend', or typos) will silently default to showing the web-app checklist, which could be confusing.

Add validation to check if the provided value is one of the accepted values ('web-app', 'api', 'cli') and show an error message with valid options if not.

Copilot · 2026-02-21T22:15:08Z

scripts/generate-prd.js

@@ -187,6 +195,7 @@ async function interactiveMode() {
  rl.close();

  const context = {};
+  context.projectType = projectTypeInput || 'web-app';


Missing input validation in interactive mode. The user can enter any string for project type, but only 'web-app', 'api', and 'cli' are valid. Invalid values will silently default to web-app behavior without warning the user.

Consider validating the input and re-prompting if an invalid value is entered, or at least show a warning that the input will be treated as 'web-app'.

Initial plan

a5f2db1

Copilot AI assigned Copilot and Krosebrook Feb 21, 2026

Copilot started work on behalf of Krosebrook February 21, 2026 01:56 View session

Clarify Vercel production-readiness audit scope: web-app vs API/CLI

e8eef13

Co-authored-by: Krosebrook <214532761+Krosebrook@users.noreply.github.com>

Copilot AI changed the title ~~[WIP] Clarify scope for Vercel production-readiness audit~~ Clarify Vercel production-readiness audit scope: web-app vs API/CLI Feb 21, 2026

Copilot AI requested a review from Krosebrook February 21, 2026 02:08

Copilot finished work on behalf of Krosebrook February 21, 2026 02:08

Krosebrook requested a review from Copilot February 21, 2026 22:11

Copilot started reviewing on behalf of Krosebrook February 21, 2026 22:11 View session

Copilot AI reviewed Feb 21, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Comments

Clarify Vercel production-readiness audit scope: web-app vs API/CLI#60

Clarify Vercel production-readiness audit scope: web-app vs API/CLI#60
Copilot wants to merge 2 commits intomainfrom
copilot/clarify-vercel-audit-scope

Copilot AI commented Feb 21, 2026 •

edited

Loading

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Feb 21, 2026

Uh oh!

Copilot AI Feb 21, 2026

Uh oh!

Copilot AI Feb 21, 2026

Uh oh!

Copilot AI Feb 21, 2026

Uh oh!

Copilot AI Feb 21, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Comments

Conversation

Copilot AI commented Feb 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Changes

scripts/generate-prd.js

src/test/generate-prd.test.js

Example

Summary by cubic

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Feb 21, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 21, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 21, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 21, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 21, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Copilot AI commented Feb 21, 2026 •

edited

Loading

`scripts/generate-prd.js`

`src/test/generate-prd.test.js`