chore: fix linting and formatting issues across repository by gaureshpai · Pull Request #68 · gaureshpai/create-next-quick

gaureshpai · 2026-02-01T13:11:30Z

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.

[2.0.1] - 2026-02-01

Fixed

Drizzle ORM: Now correctly generates .js or .ts files based on project TypeScript setting
- Previously always created .ts files even in JavaScript projects
- Config file now uses JSDoc types for JavaScript projects
Vitest Configuration: Fixed ES module compatibility issue
- Replaced __dirname with proper import.meta.url resolution
- Added required imports for path and fileURLToPath
Template Generation: Removed TypeScript-only import type { Metadata } from JavaScript layout templates
- This was causing syntax errors in JavaScript projects
Test Generation: Fixed critical bug where extracted prompts were not being added to the array
- Test cases are now properly generated from CLI prompts
Numeric Default Values: Fixed Number.isNaN() check in test generator
- Now correctly parses string values to numbers before validation
Test Diagnostics: Added stdout/stderr logging on test failures for better debugging

Changed

Async Operations: Converted run() utility function to async
- All command executions now properly await completion
- Retry delays now actually pause execution (previously were no-ops)
- Added await to all 19+ run() calls in src/index.js
Import Standardization: Migrated to node: prefix for all built-in modules
- Affects: fs, path, child_process, url, process, assert
- Improves clarity and follows Node.js best practices
Code Quality: Refactored while loops to avoid assignments in expressions
- Resolves noAssignInExpressions lint warnings
- Improved code readability

Improved

Documentation: Comprehensive README overhaul
- Added table of contents with deep links
- Expanded feature descriptions with code examples
- Added troubleshooting section
- Included project structure visualization
- Added changelog section
- Improved contributing guidelines
Documentation Site: Updated docs/index.html with missing features
- Added Testing, Authentication, and Docker to interactive prompts table
- Synchronized with README content
Error Handling: Enhanced diagnostic output in test suite
- Failed tests now display full stdout and stderr
- Easier debugging of CLI issues

Technical Debt

Cleaned up unused variables (_open in colors.js)
Removed redundant path arguments in package.json scripts
Populated PWA manifest with proper app names

[2.0.0] - 2025-12-XX

Added

Interactive Mode: Run on existing Next.js projects with -i flag
- Auto-detects project configuration (TypeScript, src dir, app dir, Tailwind)
- Only prompts for features to add (no project recreation)
Authentication Support:
- NextAuth.js (v5 Beta) with credentials provider
- Clerk with middleware setup
- Lucia auth with installation guidance
Testing Frameworks:
- Vitest with React Testing Library
- Jest with Next.js integration
- Automatic configuration and setup files
Docker Support:
- Multi-stage Dockerfile for optimized builds
- .dockerignore for efficient image creation
- Standalone output mode in next.config.mjs
Custom Prompt Implementation: Zero external dependencies
- Replaced inquirer with lightweight custom solution
- Supports input, list, and confirm prompt types
- Validation and filtering support

Changed

Error Handling: Comprehensive retry mechanism
- Automatic retries (up to 3) for failed installations
- Configurable retry delays (default 2000ms)
- Intelligent cleanup on failure
Project Cleanup: Enhanced default file removal
- Clears public folder completely
- Removes default favicon from app/src directories
- Deletes API hello route when not needed

[1.x.x] - Previous Versions

Features from v1.x

Basic Next.js project scaffolding
Package manager detection (npm, yarn, pnpm)
TypeScript and Tailwind CSS support
Multi-page generation
Linter support (ESLint, Biome)
ORM support (Prisma, Drizzle)
Shadcn UI integration
Clean project setup

Migration Guides

Migrating from 1.x to 2.x

Breaking Changes:

None! Version 2.0 is fully backward compatible

New Features to Explore:

Try interactive mode on existing projects: npx create-next-quick -i
Add authentication to your project during setup
Configure testing frameworks automatically
Enable Docker support for containerized deployments

Recommended Actions:

Update your global npm cache: npm cache clean --force
Review new authentication options if building user-facing apps
Consider adding Docker support for production deployments

Upcoming Features (Roadmap)

v2.1.0 (Planned)

v2.2.0 (Planned)

Monorepo support (Turborepo)
GraphQL setup (Apollo/Relay)
Internationalization (i18n)
PWA configuration
CI/CD templates (GitHub Actions, GitLab CI)

v3.0.0 (Future)

GUI interface for project configuration
Plugin system for custom integrations
Project templates (e-commerce, blog, SaaS)
AI-powered code generation

Support

Documentation: https://gaureshpai.github.io/create-next-quick/
Issues: https://github.com/gaureshpai/create-next-quick/issues
Discussions: https://github.com/gaureshpai/create-next-quick/discussions
Sponsor: https://patreon.com/gaureshpai

Summary by CodeRabbit

New Features
- Interactive setup adds Testing, Authentication, and Docker options.
Documentation
- Major README and docs overhaul; updated site manifest and docs formatting.
Refactor
- CLI messaging, prompts, and flows clarified and standardized across JS/TS choices.
Tests
- Enhanced test generation and harnesses with more structured cases and unified assertions.
Chores
- Project-wide formatting, quoting, and Node module specifier consistency; tooling inclusion broadened.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

coderabbitai · 2026-02-01T13:11:54Z

Warning

Rate limit exceeded

@gaureshpai has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 8 minutes and 27 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 9a9709c and 39613ef.

📒 Files selected for processing (1)

README.md

📝 Walkthrough

Walkthrough

Standardizes Node core imports to the node: namespace, normalizes quoting/formatting, makes run async with awaited retries, broadens biome.json inclusion, updates tests and test generation, and adds Testing/Authentication/Docker interactive prompt options in docs.

Changes

Cohort / File(s)	Summary
Core imports & quoting `\.github/scripts/parse-logs.js`, `src/index.js`, `src/lib/colors.js`, `src/lib/prompts.js`, `src/lib/templates.js`, `src/lib/utils.js`, `src/test/generate-tests.js`, `src/test/interactive.test.js`, `src/test/test-cases.js`, `src/test/test.js`	Replaced Node core imports with the `node:` namespace and standardized string quoting/formatting across many files. Mostly stylistic but verify runtime/node compatibility and import resolution.
Async run & call-sites `src/lib/utils.js`, `src/index.js`, callers in `src/*`	Converted `run` to `async` and added `await` at call sites; retryDelay now awaited. Confirm all call sites correctly propagate `await` and error handling remains intact.
Test generation & generated outputs `src/test/generate-tests.js`, `src/test/generated-test-cases.js`	Refactored prompt parsing and default resolution; test-case generation now uses a centralized assertion function instead of per-case assertion strings. Audit generated test shapes and any `eval` usage.
Tests & test utilities `src/test/interactive.test.js`, `src/test/test.js`, `src/test/test-cases.js`	Updated tests to use `node:` imports and adjusted test utility imports (some exports removed from `src/lib/utils.js`). Ensure tests still have required helpers or update imports.
Docs, UI prompts & assets `docs/script.js`, `docs/style.css`, `docs/site.webmanifest`, `docs/index.html`	Formatting and whitespace normalization; `docs/index.html` adds interactive prompt rows for Testing, Authentication, and Docker. Verify docs UI reflects new options and manifest formatting.
Config & README `biome.json`, `package.json`, `README.md`	Removed the file inclusion filter from `biome.json`; README restructured and package/manifest formatting changed. Review tooling implications from widened file set.
Minor templates & formatting `src/lib/templates.js`, `src/lib/colors.js`, `docs/*`	Small string/quote changes, variable rename, trailing newline and whitespace tweaks. Low-risk but scan for accidental logic changes.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~50 minutes

Possibly related PRs

feat: add interactive mode with comprehensive documentation and test coverage #67 — Overlaps edits to interactive prompts, src/index.js, src/lib/utils.js, and test generation; likely directly related.

Poem

🐇 I hopped through imports, tidy and bright,
Swapped paths to node: and set sleeps right,
Tests and docs hummed a softer tune,
Prompts grew choices under the moon,
A rabbit’s patch — small fixes, big light!

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is a detailed changelog document but does not follow the repository's required template structure (Description, Related Issue, Type of Change, Testing, Checklist, Screenshots, Additional Notes).	Restructure the PR description to match the template: add a brief summary section, link related issues, specify the type of change (this appears to be a mix of bug fixes and chores), document testing approach, and complete the provided checklist.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: fix linting and formatting issues across repository' accurately summarizes the main change—a repository-wide linting, formatting, and bug fix effort that affects multiple files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment
Commit unit tests in branch fix/lint-and-format

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

github-actions · 2026-02-01T13:15:01Z

✅ CI/CD Test Results

Overall Status: success

View full workflow run

coderabbitai

Actionable comments posted: 5

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (3)

src/lib/templates.js (1)
70-86: ⚠️ Potential issue | 🔴 Critical

TypeScript-only syntax used in JavaScript template.

The JavaScript layout template (when useTypeScript is false) includes import type { Metadata } from "next" at line 71, which is TypeScript-only syntax. This will cause a syntax error when generating .js files.
🐛 Proposed fix to remove TypeScript syntax from JS template
     : `import React from "react";
-import type { Metadata } from "next";
 import "./globals.css";

-export const metadata = {
+export const metadata = /** `@type` {import('next').Metadata} */ ({
   title: "${projectName}",
   description: "This is the ${projectName} project",
-};
+});

 export default function RootLayout({ children }) {
src/test/generate-tests.js (2)
16-50: ⚠️ Potential issue | 🔴 Critical

Critical bug: Extracted prompts are never added to extractedPrompts array.

The prompt object is created inside the inner while loop (lines 18-46) but is never pushed to extractedPrompts. As a result, extractedPrompts remains empty, and no test cases will be generated.
🐛 Proposed fix to push extracted prompts
     if (promptMatch[5]) {
       const defaultValue = promptMatch[5].trim();
       if (defaultValue === "true") {
         prompt.default = true;
       } else if (defaultValue === "false") {
         prompt.default = false;
       } else if (defaultValue === "" || defaultValue === '""') {
         prompt.default = "";
       } else if (defaultValue !== "" && !Number.isNaN(defaultValue)) {
         prompt.default = Number(defaultValue);
       } else {
         prompt.default = defaultValue.replace(/['"]/g, "");
       }
     }
+    extractedPrompts.push(prompt);
     promptMatch = promptObjectRegex.exec(promptArrayString);
   }
   promptArrayMatch = inquirerPromptRegex.exec(indexJsContent);
 }
126-138: 🧹 Nitpick | 🔵 Trivial

Generated file uses non-prefixed imports inconsistent with PR standards.

The generated test file content at lines 130-132 uses non-prefixed imports ('assert', 'fs', 'path') while the rest of the PR standardizes on node: prefixed imports.
♻️ Proposed fix for consistent imports
 const fileContent = `// This file is auto-generated by test/generate-tests.js
 // Do not edit this file directly. Run 'npm run test:generate' to regenerate.

-import { strict as assert } from 'assert';
-import fs from 'fs';
-import path from 'path';
+import { strict as assert } from "node:assert";
+import fs from "node:fs";
+import path from "node:path";

 export const testCases = ${JSON.stringify(testCases, null, 2)}.map(tc => ({

🤖 Fix all issues with AI agents

In `@docs/site.webmanifest`:
- Around line 1-11: The manifest's "name" and "short_name" are empty and should
be populated so the PWA shows an app name; update the JSON fields "name" and
"short_name" in docs/site.webmanifest (replace the empty strings for "name" and
"short_name") with meaningful values (for example "create-next-quick" and a
shorter "create-quick" or similar) ensuring the manifest remains valid JSON.

In `@package.json`:
- Line 15: The "lint" npm script currently duplicates the path argument ("biome
check . --write ."); update the "lint" script in package.json (the "lint"
property) to remove the redundant trailing "." so it reads "biome check .
--write" (retain a single path argument before the --write flag).

In `@src/lib/colors.js`:
- Around line 83-85: Remove the dead `_open` variable or use it consistently: in
the block where `_open` is defined (it computes `\x1b[38;5;${ansiCode}m`),
either delete the `_open` declaration entirely and keep the inline sequence in
the call to createBuilder([...currentStyles, `\x1b[38;5;${ansiCode}m`]), or
replace the inline string with the `_open` variable so the call becomes
createBuilder([...currentStyles, _open]) to avoid the unused variable in
colors.js (references: `_open`, `ansiCode`, `currentStyles`, `createBuilder`).

In `@src/lib/utils.js`:
- Line 23: The call to sleep in function run is not awaited so retries occur
immediately; change run to be async (declare async function run(...)) and await
sleep(retryDelay) where currently called, and then update any callers to await
run(...) so the retry delay actually pauses; alternatively, if you must keep run
synchronous implement a synchronous/blocking sleep used in run instead of the
Promise-based sleep, but the recommended fix is to make run async and await
sleep to preserve non-blocking behavior.

In `@src/test/test.js`:
- Around line 1-13: Move the "import { testCases } from \"./test-cases.js\";"
statement up with the other imports at the top of the file so all module imports
are grouped together; specifically, relocate the testCases import before the
const __filename declaration (alongside imports of spawn, assert, fileURLToPath,
path, fs, deleteFolder) while leaving the __filename, __dirname, and cliPath
variable initializations unchanged.

📜 Review details

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Cache: Disabled due to Reviews > Disable Cache setting

📥 Commits

Reviewing files that changed from the base of the PR and between f0394f5 and 8dc5e86.

📒 Files selected for processing (15)

.github/scripts/parse-logs.js
biome.json
docs/script.js
docs/site.webmanifest
docs/style.css
package.json
src/index.js
src/lib/colors.js
src/lib/prompts.js
src/lib/templates.js
src/lib/utils.js
src/test/generate-tests.js
src/test/interactive.test.js
src/test/test-cases.js
src/test/test.js

💤 Files with no reviewable changes (1)

biome.json

🧰 Additional context used

🧬 Code graph analysis (6)

src/lib/templates.js (2)

src/index.js (1)

pagesPath (396-402)

src/lib/utils.js (2)

createFolder (52-54)

createFolder (52-54)

src/test/test-cases.js (2)

src/test/generate-tests.js (1)

testCases (52-52)

src/index.js (1)

projectPath (35-35)

src/lib/prompts.js (4)

src/lib/colors.js (1)

chalk (91-91)

src/test/generate-tests.js (1)

prompt (18-24)

src/index.js (2)

answers (74-74)

answers (293-307)

src/test/interactive.test.js (4)

answers (41-41)

answers (66-66)

answers (99-99)

answers (133-133)

src/index.js (1)

src/lib/utils.js (6)

run (8-34)

run (8-34)

writeFile (36-42)

writeFile (36-42)

deleteFolder (62-66)

deleteFolder (62-66)

src/test/generate-tests.js (2)

src/lib/prompts.js (1)

prompt (110-117)

src/test/test-cases.js (2)

testCases (5-101)

testCases (5-101)

src/test/interactive.test.js (1)

src/lib/utils.js (3)

i (9-9)

readFile (44-46)

readFile (44-46)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)

GitHub Check: Node 20.x - pnpm
GitHub Check: Node 20.x - yarn
GitHub Check: Node 22.x - yarn
GitHub Check: Node 20.x - npm
GitHub Check: Node 22.x - npm
GitHub Check: Node 22.x - pnpm

🔇 Additional comments (20)

docs/style.css (1)

1-523: LGTM!

The CSS formatting changes are consistent and improve readability. Whitespace normalization and double-quote standardization applied correctly throughout.

.github/scripts/parse-logs.js (1)

1-2: LGTM!

Good modernization to use node: prefixed imports for built-in modules. This is the recommended practice in modern Node.js and helps distinguish built-ins from npm packages.

docs/script.js (1)

1-61: LGTM!

Formatting changes (semicolons, indentation, double quotes) are consistent. The code structure remains unchanged.

src/test/test-cases.js (2)

1-3: LGTM!

Import modernization to use node: prefixed built-in modules is consistent with the rest of the repository changes.

5-101: Formatting changes look good.

String quote normalization to double quotes and whitespace adjustments are consistent throughout the test cases. Test logic remains unchanged.

src/lib/prompts.js (3)

1-2: LGTM!

The import modernization to use the node: prefix for the readline module aligns with Node.js best practices and the PR's formatting objectives.

6-14: LGTM!

The getRl function correctly implements lazy initialization of the readline interface with proper formatting.

20-108: LGTM!

The processQuestion function correctly handles all three question types (confirm, list, input) with proper validation loops and default value handling. The use of Number.isNaN at line 67 is the correct choice over the global isNaN function.

src/lib/utils.js (2)

1-3: LGTM!

Import modernization to use the node: prefix is consistent with the rest of the codebase.

36-66: LGTM!

File system utility functions are correctly implemented with proper existence checks before operations.

src/lib/templates.js (1)

1-2: LGTM!

Import modernization and formatting changes are consistent with the PR objectives.

src/test/interactive.test.js (2)

1-6: LGTM!

Import modernization and cleanup of unused imports (createFolder, writeFile) are appropriate changes.

13-167: LGTM!

The interactive mode tests are well-structured with proper setup/teardown and appropriate assertions for each feature (pages, biome linter, prisma ORM, shadcn UI).

src/test/test.js (1)

30-62: LGTM!

The runTest helper function correctly manages the CLI spawn process with stdin piping for answers and proper cleanup.

src/index.js (6)

1-7: LGTM!

Import modernization to use the node: prefix and formatting standardization are consistent with the PR objectives.

12-12: LGTM!

Good practice to explicitly specify radix 10 in parseInt to avoid unexpected behavior with strings starting with "0".

86-121: LGTM!

The interactive mode detection logic correctly identifies project configuration from existing files and handles package manager detection appropriately.

352-369: Note: Retry functionality may not delay as expected.

This code calls run() with retry parameters, but as noted in src/lib/utils.js, the sleep() call in the retry logic is not awaited, so retries will occur immediately without the intended delay.

This is a cross-file concern. The fix should be applied in src/lib/utils.js as noted in that file's review.

467-505: LGTM!

Biome linter setup correctly checks for existing installation before proceeding and handles errors appropriately.

1101-1119: LGTM!

Error handling and cleanup logic correctly checks whether the project directory was created by this process before attempting cleanup, preventing accidental deletion of the user's working directory.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

coderabbitai

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In `@src/test/generate-tests.js`:
- Around line 41-42: In src/test/generate-tests.js the condition using
Number.isNaN(defaultValue) is wrong because Number.isNaN never returns true for
strings; change the logic in the block that sets prompt.default to first convert
defaultValue to a number (e.g., parsed = Number(defaultValue) or +defaultValue)
and then check that parsed is a valid number (e.g., !Number.isNaN(parsed) or
Number.isFinite(parsed)) before assigning prompt.default = parsed; keep using
the existing variables defaultValue and prompt.default to locate and replace the
failing condition.

In `@src/test/test.js`:
- Around line 31-42: The variables _stdout and _stderr are populated in the
child.stdout.on and child.stderr.on handlers but never read; either remove those
variables and the concatenation lines to avoid unnecessary memory allocation, or
keep them and use them in an assertion or diagnostic when the child exits (e.g.,
in child.on("close"/"exit") or the test completion callback) to log or assert
expected output. Locate the handlers referencing _stdout/_stderr
(child.stdout.on("data", ...) and child.stderr.on("data", ...)) and either
delete the _stdout/_stderr declarations and the "+= data.toString()" lines, or
add a final check that reads _stdout/_stderr for test assertions or error
diagnostics.

📜 Review details

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Cache: Disabled due to Reviews > Disable Cache setting

📥 Commits

Reviewing files that changed from the base of the PR and between 8dc5e86 and 12dff5f.

📒 Files selected for processing (6)

docs/site.webmanifest
src/index.js
src/lib/colors.js
src/lib/utils.js
src/test/generate-tests.js
src/test/test.js

🧰 Additional context used

🧬 Code graph analysis (2)

src/index.js (2)

src/lib/colors.js (1)

chalk (90-90)

src/lib/utils.js (10)

run (8-40)

run (8-40)

fileExists (54-56)

fileExists (54-56)

writeFile (42-48)

writeFile (42-48)

createFolder (58-60)

createFolder (58-60)

deleteFolder (68-72)

deleteFolder (68-72)

src/lib/utils.js (1)

src/lib/colors.js (1)

chalk (90-90)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)

GitHub Check: Node 20.x - npm
GitHub Check: Node 20.x - pnpm
GitHub Check: Node 22.x - pnpm
GitHub Check: Node 22.x - yarn
GitHub Check: Node 22.x - npm
GitHub Check: Node 20.x - yarn

🔇 Additional comments (7)

src/lib/colors.js (1)

83-84: LGTM! Previous issue addressed.

The _open variable is now properly used in the createBuilder call, resolving the previously flagged dead code issue.

src/test/test.js (1)

1-7: LGTM! Import ordering issue resolved.

All imports are now properly grouped at the top of the file, addressing the previous review feedback.

src/lib/utils.js (1)

8-40: LGTM! Critical async/await issue resolved.

The run function is now properly async and await sleep(retryDelay) on line 29 ensures retry delays work as intended. The callers in src/index.js have been updated accordingly.

src/index.js (2)

1-7: LGTM! Modernized imports and consistent async handling.

The migration to node: namespace imports and proper await usage on all run() calls throughout the file is correctly implemented.

12-12: Good practice: explicit radix in parseInt.

Using parseInt(value, 10) with explicit radix prevents unexpected behavior with strings starting with "0".

src/test/generate-tests.js (2)

1-5: LGTM! Modernized imports.

Node.js namespace imports are correctly applied.

135-138: Use of eval() is acceptable here but worth noting.

The eval(tc.assertions) is used within a controlled test generation context where the assertion strings are generated by this same script. While eval() is generally discouraged, this usage is acceptable for test scaffolding purposes since the input is not user-controlled.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

…cts with configurable features and accompanying documentation.

coderabbitai

Actionable comments posted: 10

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

src/test/generate-tests.js (1)

138-141: 🧹 Nitpick | 🔵 Trivial

Using eval() for assertions works but limits flexibility.

The current approach stores assertions as strings and evaluates them at runtime. This works for simple assertions but has limitations:

No IDE support (syntax highlighting, error checking) for assertion code

Harder to debug if assertions fail

Consider whether the assertions need to be serialized as strings, or if the generated file could contain actual function bodies.

🤖 Fix all issues with AI agents

In `@README.md`:
- Around line 71-92: README.md has headings and fenced code blocks missing
surrounding blank lines (MD022/MD031); update the file to add a blank line after
each top-level or subsection heading (e.g., "### 🏗️ Project Scaffolding", "###
🛠️ Tooling & Integrations", "Advanced Features", "Troubleshooting") and ensure
there is an empty line before and after any fenced code block; scan the Advanced
Features and Troubleshooting sections and insert the missing blank lines
consistently so each heading is followed by one blank line and each code fence
has a blank line above and below.
- Around line 407-410: The contributors image <img
src="https://contrib.rocks/image?repo=gaureshpai/create-next-quick" /> is
missing an alt attribute; add a meaningful alt value to the <img> element (for
example "Contributors to create-next-quick on GitHub" or similar) to improve
screen-reader accessibility while keeping the descriptive text brief and
relevant.
- Around line 318-322: Replace the "Permission Errors" example that suggests
using "sudo npx create-next-quick my-app" with guidance that recommends safer
alternatives: advise using a Node version manager (nvm/fnm) to avoid global
permission issues, instruct users to fix npm permissions by setting a user-local
npm prefix, and tell users to create projects in user-owned directories; remove
the explicit "sudo npx ..." line and update the section header/content
accordingly (look for the "Permission Errors" section and the example showing
"sudo npx create-next-quick my-app").
- Around line 39-42: The Table of Contents contains two invalid entries:
"[Project Structure](`#-project-structure`)" and "[Changelog](`#-changelog`)";
either add matching headings "Project Structure" and "Changelog" to the README
(using exact heading text so the anchor IDs match) or remove those two lines
from the TOC; update the TOC entries to match existing headings if you prefer
different titles (ensure anchors like "#project-structure" and "#changelog" are
correct if you change wording).

In `@src/index.js`:
- Around line 939-943: The Vitest config generation hardcodes the '@' alias to
'./src' causing imports to break when useSrcDir is false; update the
vitestConfigContent generation so the resolve.alias for '@' uses the useSrcDir
flag (e.g., interpolate '${useSrcDir ? "./src" : "."}') instead of always
'./src' so the alias points to project root when no src directory exists; locate
the vitestConfigContent template string in src/index.js and modify the alias
line inside the resolve block accordingly, keeping other fields (setupFiles,
useTypeScript) unchanged.
- Line 972: The call to run(`${packageManager} install --save-dev ${deps.join("
")}`, projectPath, false) lacks error handling; update the code around the run
invocation that installs Jest dev deps to capture the returned result or catch
thrown errors from run() (the same pattern used for the Vitest setup), check
whether the installation succeeded, and on failure log an informative error via
the existing logger or processLogger and abort (throw or process.exit(1)) with
context including packageManager, deps, and projectPath so failures are
detectable and consistent with other setup flows.
- Line 1006: The install call await run(`${packageManager} install
next-auth@beta`, projectPath, false) lacks error handling; wrap this run
invocation (and the other two identical auth installs) in the same
error-checking pattern used for ORM/linter setup: either try/catch the await
run(...) and on failure call the existing logger/processLogger.error with the
error details and exit (process.exit(1)) or check the run result and bail
similarly. Update the three locations that call run(...) with packageManager,
projectPath and next-auth@beta to use that pattern so failures are logged with
the error and the process terminates.
- Line 923: The await run(installCmd, projectPath, false) call currently ignores
failures; change it to capture the result (e.g., const result = await
run(installCmd, projectPath, false)) and then check result.success like other
run() usages in this file, logging an error and exiting/throwing when
installation fails so a missing Vitest dependency is reported immediately (refer
to the run function call and the installCmd and projectPath variables to locate
the call).

In `@src/test/generate-tests.js`:
- Around line 69-73: The repeated ternary for resolving prompt defaults
(p.default !== undefined ? p.default : p.type === "confirm" ? false : "") used
when populating enableTestCase.options from extractedPrompts should be extracted
into a small helper (e.g., getPromptDefault or resolveDefaultForPrompt) that
accepts a prompt object and returns the correct default; replace all four
occurrences (the loops referencing extractedPrompts and assignments to
enableTestCase.options) with calls to this helper to centralize the logic and
improve maintainability.

In `@src/test/test.js`:
- Around line 44-53: The interval loop writing answers to the child process
(variables i, interval, answers and calls to child.stdin.write) can attempt
writes after the child has exited; add robustness by registering a 'close'
(and/or 'exit' and 'error') handler on child to call clearInterval(interval) and
ensure child.stdin is ended, and before each write check child.stdin.writable
(or wrap child.stdin.write in a try/catch and guard with if (!child.killed) to
avoid throws); also attach an 'error' listener on child and child.stdin to stop
the interval and handle/propagate the error instead of letting the interval
continue.

📜 Review details

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Cache: Disabled due to Reviews > Disable Cache setting

📥 Commits

Reviewing files that changed from the base of the PR and between 12dff5f and 9d13ce1.

📒 Files selected for processing (5)

README.md
docs/index.html
src/index.js
src/test/generate-tests.js
src/test/test.js

🧰 Additional context used

🧬 Code graph analysis (3)

src/test/test.js (4)

src/test/interactive.test.js (12)

__filename (8-8)

__dirname (9-9)

cliPath (11-11)

i (44-44)

i (70-70)

i (103-103)

i (137-137)

i (174-174)

answers (41-41)

answers (66-66)

answers (99-99)

answers (133-133)

src/lib/utils.js (1)

i (15-15)

src/index.js (2)

answers (74-74)

answers (293-307)

src/lib/prompts.js (1)

answers (111-111)

src/test/generate-tests.js (2)

src/lib/prompts.js (1)

prompt (110-117)

src/test/test-cases.js (2)

testCases (5-101)

testCases (5-101)

src/index.js (1)

src/lib/utils.js (10)

run (8-40)

run (8-40)

fileExists (54-56)

fileExists (54-56)

writeFile (42-48)

writeFile (42-48)

createFolder (58-60)

createFolder (58-60)

deleteFolder (68-72)

deleteFolder (68-72)

🪛 markdownlint-cli2 (0.20.0)

README.md

[warning] 31-31: Link fragments should be valid

(MD051, link-fragments)

[warning] 39-39: Link fragments should be valid

(MD051, link-fragments)

[warning] 42-42: Link fragments should be valid

(MD051, link-fragments)

[warning] 54-54: Table column style
Table pipe does not align with header for style "aligned"

(MD060, table-column-style)

[warning] 54-54: Table column style
Table pipe does not align with header for style "aligned"

(MD060, table-column-style)

[warning] 55-55: Table column style
Table pipe does not align with header for style "aligned"

(MD060, table-column-style)

[warning] 55-55: Table column style
Table pipe does not align with header for style "aligned"

(MD060, table-column-style)

[warning] 56-56: Table column style
Table pipe does not align with header for style "aligned"

(MD060, table-column-style)

[warning] 56-56: Table column style
Table pipe does not align with header for style "aligned"

(MD060, table-column-style)

[warning] 57-57: Table column style
Table pipe does not align with header for style "aligned"

(MD060, table-column-style)

[warning] 57-57: Table column style
Table pipe does not align with header for style "aligned"

(MD060, table-column-style)

[warning] 58-58: Table column style
Table pipe does not align with header for style "aligned"

(MD060, table-column-style)

[warning] 58-58: Table column style
Table pipe does not align with header for style "aligned"

(MD060, table-column-style)

[warning] 59-59: Table column style
Table pipe does not align with header for style "aligned"

(MD060, table-column-style)

[warning] 59-59: Table column style
Table pipe does not align with header for style "aligned"

(MD060, table-column-style)

[warning] 60-60: Table column style
Table pipe does not align with header for style "aligned"

(MD060, table-column-style)

[warning] 60-60: Table column style
Table pipe does not align with header for style "aligned"

(MD060, table-column-style)

[warning] 61-61: Table column style
Table pipe does not align with header for style "aligned"

(MD060, table-column-style)

[warning] 61-61: Table column style
Table pipe does not align with header for style "aligned"

(MD060, table-column-style)

[warning] 62-62: Table column style
Table pipe does not align with header for style "aligned"

(MD060, table-column-style)

[warning] 62-62: Table column style
Table pipe does not align with header for style "aligned"

(MD060, table-column-style)

[warning] 63-63: Table column style
Table pipe does not align with header for style "aligned"

(MD060, table-column-style)

[warning] 63-63: Table column style
Table pipe does not align with header for style "aligned"

(MD060, table-column-style)

[warning] 64-64: Table column style
Table pipe does not align with header for style "aligned"

(MD060, table-column-style)

[warning] 64-64: Table column style
Table pipe does not align with header for style "aligned"

(MD060, table-column-style)

[warning] 65-65: Table column style
Table pipe does not align with header for style "aligned"

(MD060, table-column-style)

[warning] 65-65: Table column style
Table pipe does not align with header for style "aligned"

(MD060, table-column-style)

[warning] 71-71: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below