create-apppaaaul 2.0.19 → 2.0.21

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-apppaaaul",
-  "version": "2.0.19",
+  "version": "2.0.21",
   "description": "Create projects as paaauldev would",
   "main": "index.mjs",
   "bin": {
@@ -33,11 +33,11 @@
     "bump": "pnpm run build && pnpm version patch && git tag latest --force && git push origin main --tags --force && npm publish --tag latest --force"
   },
   "devDependencies": {
-    "@types/node": "^20.17.27",
+    "@types/node": "^24.9.1",
     "@types/prompts": "^2.4.9",
-    "@types/yargs": "^17.0.33",
-    "prettier": "^3.5.3",
-    "tsup": "^8.4.0",
-    "typescript": "^5.8.2"
+    "@types/yargs": "^17.0.34",
+    "prettier": "^3.6.2",
+    "tsup": "^8.5.0",
+    "typescript": "^5.9.3"
   }
 }

package/dist/templates/nextjs-ts-landing/project/.editorconfig

@@ -1,9 +0,0 @@
-root = true
-
-[*]
-insert_final_newline = true
-charset = utf-8
-indent_style = space
-indent_size = 2
-trim_trailing_whitespace = true
-max_line_length = 80

package/dist/templates/nextjs-ts-landing/project/.eslintrc.mjs

@@ -1,172 +0,0 @@
-import globals from "globals";
-import tseslint from "typescript-eslint";
-import eslintPluginReact from "eslint-plugin-react";
-import eslintPluginReactHooks from "eslint-plugin-react-hooks";
-import {fixupPluginRules} from "@eslint/compat";
-import eslintPluginPrettier from "eslint-plugin-prettier/recommended";
-import eslintPluginImport from "eslint-plugin-import";
-import eslintPluginReactCompiler from "eslint-plugin-react-compiler";
-import eslintPluginNext from "@next/eslint-plugin-next";
-import eslintPluginJsxA11y from "eslint-plugin-jsx-a11y";
-import vercelStyleGuideTypescript from "@vercel/style-guide/eslint/typescript";
-import vercelStyleGuideReact from "@vercel/style-guide/eslint/rules/react";
-import vercelStyleGuideNext from "@vercel/style-guide/eslint/next";
-
-export default [
-  // Ignores configuration
-  {
-    ignores: ["node_modules", ".next", "out", "coverage", ".idea"],
-  },
-  // General configuration
-  {
-    rules: {
-      "padding-line-between-statements": [
-        "warn",
-        {blankLine: "always", prev: "*", next: ["return", "export"]},
-        {blankLine: "always", prev: ["const", "let", "var"], next: "*"},
-        {blankLine: "any", prev: ["const", "let", "var"], next: ["const", "let", "var"]},
-      ],
-      "no-console": "warn",
-    },
-  },
-  // React configuration
-  {
-    plugins: {
-      react: fixupPluginRules(eslintPluginReact),
-      "react-hooks": fixupPluginRules(eslintPluginReactHooks),
-      "react-compiler": fixupPluginRules(eslintPluginReactCompiler),
-      "jsx-a11y": fixupPluginRules(eslintPluginJsxA11y),
-    },
-    languageOptions: {
-      parserOptions: {
-        ecmaFeatures: {
-          jsx: true,
-        },
-      },
-      globals: {
-        ...globals.browser,
-        ...globals.serviceworker,
-      },
-    },
-    settings: {
-      react: {
-        version: "detect",
-      },
-    },
-    rules: {
-      ...eslintPluginReact.configs.recommended.rules,
-      ...eslintPluginJsxA11y.configs.recommended.rules,
-      ...eslintPluginReactHooks.configs.recommended.rules,
-      ...vercelStyleGuideReact.rules,
-      "react/prop-types": "off",
-      "react/jsx-uses-react": "off",
-      "react/react-in-jsx-scope": "off",
-      "react/self-closing-comp": "warn",
-      "react/jsx-sort-props": [
-        "warn",
-        {
-          callbacksLast: true,
-          shorthandFirst: true,
-          noSortAlphabetically: false,
-          reservedFirst: true,
-        },
-      ],
-      "react-compiler/react-compiler": "error",
-      "jsx-a11y/no-static-element-interactions": "off",
-      "jsx-a11y/click-events-have-key-events": "off",
-    },
-  },
-  // TypeScript configuration
-  ...[
-    ...tseslint.configs.recommended,
-    {
-      rules: {
-        ...vercelStyleGuideTypescript.rules,
-        "@typescript-eslint/no-non-null-assertion": "off",
-        "@typescript-eslint/no-shadow": "off",
-        "@typescript-eslint/explicit-function-return-type": "off",
-        "@typescript-eslint/require-await": "off",
-        "@typescript-eslint/no-floating-promises": "off",
-        "@typescript-eslint/no-confusing-void-expression": "off",
-        "@typescript-eslint/no-unused-vars": [
-          "warn",
-          {
-            args: "after-used",
-            ignoreRestSiblings: false,
-            argsIgnorePattern: "^_.*?$",
-          },
-        ],
-      },
-    },
-  ],
-  // Prettier configuration
-  ...[
-    eslintPluginPrettier,
-    {
-      rules: {
-        "prettier/prettier": [
-          "warn",
-          {
-            printWidth: 100,
-            trailingComma: "all",
-            tabWidth: 2,
-            semi: true,
-            singleQuote: false,
-            bracketSpacing: true,
-            arrowParens: "always",
-            endOfLine: "auto",
-            plugins: ["prettier-plugin-tailwindcss"],
-          },
-        ],
-      },
-    },
-  ],
-  // Import configuration
-  {
-    plugins: {
-      import: fixupPluginRules(eslintPluginImport),
-    },
-    rules: {
-      "import/no-default-export": "off",
-      "import/order": [
-        "warn",
-        {
-          groups: [
-            "type",
-            "builtin",
-            "object",
-            "external",
-            "internal",
-            "parent",
-            "sibling",
-            "index",
-          ],
-          pathGroups: [
-            {
-              pattern: "~/**",
-              group: "external",
-              position: "after",
-            },
-          ],
-          "newlines-between": "always",
-        },
-      ],
-    },
-  },
-  // Next configuration
-  {
-    plugins: {
-      next: fixupPluginRules(eslintPluginNext),
-    },
-    languageOptions: {
-      globals: {
-        ...globals.node,
-        ...globals.browser,
-      },
-    },
-    rules: {
-      ...vercelStyleGuideNext.rules,
-      "@next/next/no-img-element": "off",
-    },
-  },
-];

package/dist/templates/nextjs-ts-landing/project/.vscode/launch.json

@@ -1,28 +0,0 @@
-{
-  "version": "0.2.0",
-  "configurations": [
-    {
-      "name": "Next.js: debug server-side",
-      "type": "node-terminal",
-      "request": "launch",
-      "command": "pnpm dev"
-    },
-    {
-      "name": "Next.js: debug client-side",
-      "type": "chrome",
-      "request": "launch",
-      "url": "http://localhost:3000"
-    },
-    {
-      "name": "Next.js: debug full stack",
-      "type": "node-terminal",
-      "request": "launch",
-      "command": "pnpm dev",
-      "serverReadyAction": {
-        "pattern": "started server on .+, url: (https?://.+)",
-        "uriFormat": "%s",
-        "action": "debugWithChrome"
-      }
-    }
-  ]
-}

package/dist/templates/nextjs-ts-landing/project/.vscode/settings.json

@@ -1,8 +0,0 @@
-{
-  "editor.formatOnSave": false,
-  "typescript.tsdk": "node_modules\\typescript\\lib",
-  "typescript.enablePromptUseWorkspaceTsdk": true,
-  "editor.codeActionsOnSave": {
-    "source.fixAll.eslint": true
-  }
-}

package/dist/templates/nextjs-ts-landing-drizzle/project/.cursor/rules/bootstrap-cursor-rules.mdc

@@ -1,45 +0,0 @@
----
-description: Bootstrap Cursor Rules
-globs:
-alwaysApply: false
----
-You are an expert in Bootstrap and modern web application development.
-
-    Key Principles
-    - Write clear, concise, and technical responses with precise Bootstrap examples.
-    - Utilize Bootstrap's components and utilities to streamline development and ensure responsiveness.
-    - Prioritize maintainability and readability; adhere to clean coding practices throughout your HTML and CSS.
-    - Use descriptive class names and structure to promote clarity and collaboration among developers.
-
-    Bootstrap Usage
-    - Leverage Bootstrap's grid system for responsive layouts; use container, row, and column classes to structure content.
-    - Utilize Bootstrap components (e.g., buttons, modals, alerts) to enhance user experience without extensive custom CSS.
-    - Apply Bootstrap's utility classes for quick styling adjustments, such as spacing, typography, and visibility.
-    - Ensure all components are accessible; use ARIA attributes and semantic HTML where applicable.
-
-    Error Handling and Validation
-    - Implement form validation using Bootstrap's built-in styles and classes to enhance user feedback.
-    - Use Bootstrap's alert component to display error messages clearly and informatively.
-    - Structure forms with appropriate labels, placeholders, and error messages for a better user experience.
-
-    Dependencies
-    - Bootstrap (latest version, CSS and JS)
-    - Any JavaScript framework (like jQuery, if required) for interactive components.
-
-    Bootstrap-Specific Guidelines
-    - Customize Bootstrap's Sass variables and mixins to create a unique theme without overriding default styles.
-    - Utilize Bootstrap's responsive utilities to control visibility and layout on different screen sizes.
-    - Keep custom styles to a minimum; use Bootstrap's classes wherever possible for consistency.
-    - Use the Bootstrap documentation to understand component behavior and customization options.
-
-    Performance Optimization
-    - Minimize file sizes by including only the necessary Bootstrap components in your build process.
-    - Use a CDN for Bootstrap resources to improve load times and leverage caching.
-    - Optimize images and other assets to enhance overall performance, especially for mobile users.
-
-    Key Conventions
-    1. Follow Bootstrap's naming conventions and class structures to ensure consistency across your project.
-    2. Prioritize responsiveness and accessibility in every stage of development.
-    3. Maintain a clear and organized file structure to enhance maintainability and collaboration.
-
-    Refer to the Bootstrap documentation for best practices and detailed examples of usage patterns.

package/dist/templates/nextjs-ts-landing-drizzle/project/.cursor/rules/front-end-cursor-rules.mdc

@@ -1,38 +0,0 @@
----
-description: Front-End Developer
-globs:
-alwaysApply: false
----
-You are a Senior Front-End Developer and an Expert in ReactJS, NextJS, JavaScript, TypeScript, HTML, CSS and modern UI/UX frameworks (e.g., TailwindCSS, Shadcn, Radix). You are thoughtful, give nuanced answers, and are brilliant at reasoning. You carefully provide accurate, factual, thoughtful answers, and are a genius at reasoning.
-
-- Follow the user’s requirements carefully & to the letter.
-- First think step-by-step - describe your plan for what to build in pseudocode, written out in great detail.
-- Confirm, then write code!
-- Always write correct, best practice, DRY principle (Dont Repeat Yourself), bug free, fully functional and working code also it should be aligned to listed rules down below at Code Implementation Guidelines .
-- Focus on easy and readability code, over being performant.
-- Fully implement all requested functionality.
-- Leave NO todo’s, placeholders or missing pieces.
-- Ensure code is complete! Verify thoroughly finalised.
-- Include all required imports, and ensure proper naming of key components.
-- Be concise Minimize any other prose.
-- If you think there might not be a correct answer, you say so.
-- If you do not know the answer, say so, instead of guessing.
-
-### Coding Environment
-The user asks questions about the following coding languages:
-- ReactJS
-- NextJS
-- JavaScript
-- TypeScript
-- TailwindCSS
-- HTML
-- CSS
-
-### Code Implementation Guidelines
-Follow these rules when you write code:
-- Use early returns whenever possible to make the code more readable.
-- Always use Tailwind classes for styling HTML elements; avoid using CSS or tags.
-- Use “class:” instead of the tertiary operator in class tags whenever possible.
-- Use descriptive variable and function/const names. Also, event functions should be named with a “handle” prefix, like “handleClick” for onClick and “handleKeyDown” for onKeyDown.
-- Implement accessibility features on elements. For example, a tag should have a tabindex=“0”, aria-label, on:click, and on:keydown, and similar attributes.
-- Use consts instead of functions, for example, “const toggle = () =>”. Also, define a type if possible.

package/dist/templates/nextjs-ts-landing-drizzle/project/.cursor/rules/optimized-nextjs-typescript-best-practices-modern-ui-ux.mdc

@@ -1,58 +0,0 @@
----
-description: Optimized Next.js TypeScript Best Practices with Modern UI/UX
-globs:
-alwaysApply: false
----
-You are an expert full-stack developer proficient in TypeScript, React, Next.js, and modern UI/UX frameworks (e.g., Tailwind CSS, Shadcn UI, Radix UI). Your task is to produce the most optimized and maintainable Next.js code, following best practices and adhering to the principles of clean code and robust architecture.
-
-    ### Objective
-    - Create a Next.js solution that is not only functional but also adheres to the best practices in performance, security, and maintainability.
-
-    ### Code Style and Structure
-    - Write concise, technical TypeScript code with accurate examples.
-    - Use functional and declarative programming patterns; avoid classes.
-    - Favor iteration and modularization over code duplication.
-    - Use descriptive variable names with auxiliary verbs (e.g., `isLoading`, `hasError`).
-    - Structure files with exported components, subcomponents, helpers, static content, and types.
-    - Use lowercase with dashes for directory names (e.g., `components/auth-wizard`).
-
-    ### Optimization and Best Practices
-    - Minimize the use of `'use client'`, `useEffect`, and `setState`; favor React Server Components (RSC) and Next.js SSR features.
-    - Implement dynamic imports for code splitting and optimization.
-    - Use responsive design with a mobile-first approach.
-    - Optimize images: use WebP format, include size data, implement lazy loading.
-
-    ### Error Handling and Validation
-    - Prioritize error handling and edge cases:
-      - Use early returns for error conditions.
-      - Implement guard clauses to handle preconditions and invalid states early.
-      - Use custom error types for consistent error handling.
-
-    ### UI and Styling
-    - Use modern UI frameworks (e.g., Tailwind CSS, Shadcn UI, Radix UI) for styling.
-    - Implement consistent design and responsive patterns across platforms.
-
-    ### State Management and Data Fetching
-    - Use modern state management solutions (e.g., Zustand, TanStack React Query) to handle global state and data fetching.
-    - Implement validation using Zod for schema validation.
-
-    ### Security and Performance
-    - Implement proper error handling, user input validation, and secure coding practices.
-    - Follow performance optimization techniques, such as reducing load times and improving rendering efficiency.
-
-    ### Testing and Documentation
-    - Write unit tests for components using Jest and React Testing Library.
-    - Provide clear and concise comments for complex logic.
-    - Use JSDoc comments for functions and components to improve IDE intellisense.
-
-    ### Methodology
-    1. **System 2 Thinking**: Approach the problem with analytical rigor. Break down the requirements into smaller, manageable parts and thoroughly consider each step before implementation.
-    2. **Tree of Thoughts**: Evaluate multiple possible solutions and their consequences. Use a structured approach to explore different paths and select the optimal one.
-    3. **Iterative Refinement**: Before finalizing the code, consider improvements, edge cases, and optimizations. Iterate through potential enhancements to ensure the final solution is robust.
-
-    **Process**:
-    1. **Deep Dive Analysis**: Begin by conducting a thorough analysis of the task at hand, considering the technical requirements and constraints.
-    2. **Planning**: Develop a clear plan that outlines the architectural structure and flow of the solution, using <PLANNING> tags if necessary.
-    3. **Implementation**: Implement the solution step-by-step, ensuring that each part adheres to the specified best practices.
-    4. **Review and Optimize**: Perform a review of the code, looking for areas of potential optimization and improvement.
-    5. **Finalization**: Finalize the code by ensuring it meets all requirements, is secure, and is performant.

package/dist/templates/nextjs-ts-landing-drizzle/project/.editorconfig

@@ -1,9 +0,0 @@
-root = true
-
-[*]
-insert_final_newline = true
-charset = utf-8
-indent_style = space
-indent_size = 2
-trim_trailing_whitespace = true
-max_line_length = 80

package/dist/templates/nextjs-ts-landing-drizzle/project/.eslintrc.mjs

@@ -1,172 +0,0 @@
-import globals from "globals";
-import tseslint from "typescript-eslint";
-import eslintPluginReact from "eslint-plugin-react";
-import eslintPluginReactHooks from "eslint-plugin-react-hooks";
-import {fixupPluginRules} from "@eslint/compat";
-import eslintPluginPrettier from "eslint-plugin-prettier/recommended";
-import eslintPluginImport from "eslint-plugin-import";
-import eslintPluginReactCompiler from "eslint-plugin-react-compiler";
-import eslintPluginNext from "@next/eslint-plugin-next";
-import eslintPluginJsxA11y from "eslint-plugin-jsx-a11y";
-import vercelStyleGuideTypescript from "@vercel/style-guide/eslint/typescript";
-import vercelStyleGuideReact from "@vercel/style-guide/eslint/rules/react";
-import vercelStyleGuideNext from "@vercel/style-guide/eslint/next";
-
-export default [
-  // Ignores configuration
-  {
-    ignores: ["node_modules", ".next", "out", "coverage", ".idea"],
-  },
-  // General configuration
-  {
-    rules: {
-      "padding-line-between-statements": [
-        "warn",
-        {blankLine: "always", prev: "*", next: ["return", "export"]},
-        {blankLine: "always", prev: ["const", "let", "var"], next: "*"},
-        {blankLine: "any", prev: ["const", "let", "var"], next: ["const", "let", "var"]},
-      ],
-      "no-console": "warn",
-    },
-  },
-  // React configuration
-  {
-    plugins: {
-      react: fixupPluginRules(eslintPluginReact),
-      "react-hooks": fixupPluginRules(eslintPluginReactHooks),
-      "react-compiler": fixupPluginRules(eslintPluginReactCompiler),
-      "jsx-a11y": fixupPluginRules(eslintPluginJsxA11y),
-    },
-    languageOptions: {
-      parserOptions: {
-        ecmaFeatures: {
-          jsx: true,
-        },
-      },
-      globals: {
-        ...globals.browser,
-        ...globals.serviceworker,
-      },
-    },
-    settings: {
-      react: {
-        version: "detect",
-      },
-    },
-    rules: {
-      ...eslintPluginReact.configs.recommended.rules,
-      ...eslintPluginJsxA11y.configs.recommended.rules,
-      ...eslintPluginReactHooks.configs.recommended.rules,
-      ...vercelStyleGuideReact.rules,
-      "react/prop-types": "off",
-      "react/jsx-uses-react": "off",
-      "react/react-in-jsx-scope": "off",
-      "react/self-closing-comp": "warn",
-      "react/jsx-sort-props": [
-        "warn",
-        {
-          callbacksLast: true,
-          shorthandFirst: true,
-          noSortAlphabetically: false,
-          reservedFirst: true,
-        },
-      ],
-      "react-compiler/react-compiler": "error",
-      "jsx-a11y/no-static-element-interactions": "off",
-      "jsx-a11y/click-events-have-key-events": "off",
-    },
-  },
-  // TypeScript configuration
-  ...[
-    ...tseslint.configs.recommended,
-    {
-      rules: {
-        ...vercelStyleGuideTypescript.rules,
-        "@typescript-eslint/no-non-null-assertion": "off",
-        "@typescript-eslint/no-shadow": "off",
-        "@typescript-eslint/explicit-function-return-type": "off",
-        "@typescript-eslint/require-await": "off",
-        "@typescript-eslint/no-floating-promises": "off",
-        "@typescript-eslint/no-confusing-void-expression": "off",
-        "@typescript-eslint/no-unused-vars": [
-          "warn",
-          {
-            args: "after-used",
-            ignoreRestSiblings: false,
-            argsIgnorePattern: "^_.*?$",
-          },
-        ],
-      },
-    },
-  ],
-  // Prettier configuration
-  ...[
-    eslintPluginPrettier,
-    {
-      rules: {
-        "prettier/prettier": [
-          "warn",
-          {
-            printWidth: 100,
-            trailingComma: "all",
-            tabWidth: 2,
-            semi: true,
-            singleQuote: false,
-            bracketSpacing: true,
-            arrowParens: "always",
-            endOfLine: "auto",
-            plugins: ["prettier-plugin-tailwindcss"],
-          },
-        ],
-      },
-    },
-  ],
-  // Import configuration
-  {
-    plugins: {
-      import: fixupPluginRules(eslintPluginImport),
-    },
-    rules: {
-      "import/no-default-export": "off",
-      "import/order": [
-        "warn",
-        {
-          groups: [
-            "type",
-            "builtin",
-            "object",
-            "external",
-            "internal",
-            "parent",
-            "sibling",
-            "index",
-          ],
-          pathGroups: [
-            {
-              pattern: "~/**",
-              group: "external",
-              position: "after",
-            },
-          ],
-          "newlines-between": "always",
-        },
-      ],
-    },
-  },
-  // Next configuration
-  {
-    plugins: {
-      next: fixupPluginRules(eslintPluginNext),
-    },
-    languageOptions: {
-      globals: {
-        ...globals.node,
-        ...globals.browser,
-      },
-    },
-    rules: {
-      ...vercelStyleGuideNext.rules,
-      "@next/next/no-img-element": "off",
-    },
-  },
-];

package/dist/templates/nextjs-ts-landing-drizzle/project/.vscode/launch.json

@@ -1,28 +0,0 @@
-{
-  "version": "0.2.0",
-  "configurations": [
-    {
-      "name": "Next.js: debug server-side",
-      "type": "node-terminal",
-      "request": "launch",
-      "command": "pnpm dev"
-    },
-    {
-      "name": "Next.js: debug client-side",
-      "type": "chrome",
-      "request": "launch",
-      "url": "http://localhost:3000"
-    },
-    {
-      "name": "Next.js: debug full stack",
-      "type": "node-terminal",
-      "request": "launch",
-      "command": "pnpm dev",
-      "serverReadyAction": {
-        "pattern": "started server on .+, url: (https?://.+)",
-        "uriFormat": "%s",
-        "action": "debugWithChrome"
-      }
-    }
-  ]
-}

package/dist/templates/nextjs-ts-landing-drizzle/project/.vscode/settings.json

@@ -1,8 +0,0 @@
-{
-  "editor.formatOnSave": false,
-  "typescript.tsdk": "node_modules\\typescript\\lib",
-  "typescript.enablePromptUseWorkspaceTsdk": true,
-  "editor.codeActionsOnSave": {
-    "source.fixAll.eslint": "explicit"
-  }
-}