nuxt/nuxt

AI Summary: With the upgrade to Nuxt v4, IDEs are flagging auto-imports within extended folders (layers or `extends` configuration) as missing, leading to lint warnings. This issue is a regression, as reverting to Nuxt v3.17.7 resolves the problem, suggesting a change in how v4 handles module resolution or `tsconfig` generation for layered projects.

AI Summary: This GitHub issue proposes documenting clear rules for tag placement, indentation, and general code writing standards within the project's documentation. Specifically, it calls for consistent tag placement and spacing, and ensuring all `<script setup>` blocks include `lang="ts"`. The overarching goal is to enhance documentation consistency and code quality, with a strong suggestion to implement automated tests or rules to enforce these standards.

AI Summary: Update the Nuxt v4 documentation to correct references to v3. Specifically, instances of `3.0.0` and similar version numbers within the linked documentation section on nightly releases should be updated to reflect the correct v4.x.x versioning.

AI Summary: Implement a warning in the Nuxt development environment when a developer uses the `hydrate` directive without the `Lazy` prefix on a component, indicating that the component should be wrapped with `Lazy` for correct hydration behavior.

AI Summary: Add a short section to Nuxt's contribution guidelines and pull request template advising on the ethical and responsible use of AI tools for code generation and writing, emphasizing that AI should be used as an assistant, not a replacement for human understanding and authorship.

AI Summary: Debug and fix a Nuxt.js bug where `definePageMeta` is ignored in pages located in directories containing '.js' in their names, especially when using TypeScript and pnpm. The issue stems from incorrect file type inference by the parser, leading to missing page metadata like middleware. The solution involves modifying the Nuxt.js parser to correctly handle TypeScript files even when the parent directory name includes '.js'.

AI Summary: The issue requests the implementation of a feature in the Nuxt framework to allow payload extraction for non-prerendered pages, specifically enabling improved caching with ISR (Incremental Static Regeneration). This would enhance performance by reducing API calls and leveraging CDN caching for static pages. The task involves investigating the feasibility of adding this functionality, potentially as a module, and considering its impact on existing Nuxt features.

AI Summary: The task is to implement a feature in the Nuxt.js framework (v4) that enforces a strict directory structure. This prevents compatibility mode fallbacks from masking misplaced files, improving code organization and maintainability for developers. The implementation could potentially be as a module.

AI Summary: The task requires implementing a feature in the Nuxt framework that allows adding aliases to the shared TypeScript configuration (`tsconfig.json`) file. Currently, aliases defined in `nuxt.config` do not affect the shared directory's TypeScript compilation. The solution might involve modifying Nuxt's internal build process or creating a module to handle alias injection into the shared `tsconfig.json`.

AI Summary: Investigate and debug a Nuxt 3.17.7 router issue where `scrollBehaviorType: 'smooth'` unexpectedly causes smooth scrolling to the top of the page even when navigating between pages with non-hash links. The issue appears to be related to recent changes in Nuxt's router implementation. The task involves analyzing provided reproduction code (StackBlitz link), comparing behavior with Nuxt 3.17.6, and potentially identifying and proposing a fix or workaround.

AI Summary: The task requires modifying the Nuxt 4 build process to include shared type definitions from a `shared` directory in the generated `tsconfig.server.json` file. This ensures type consistency between client-side and server-side code, fixing a bug where server routes cannot access types defined in the shared directory.

AI Summary: Debug and fix a bug in Nuxt 3 where the `clear` function doesn't cancel pending `useFetch` requests. This involves analyzing provided reproduction code (StackBlitz link), understanding Nuxt's `useFetch` and its cancellation mechanism, and implementing a solution to ensure requests are properly aborted when `clear` is called.

AI Summary: The task is to fix a bug in Nuxt 3's error handling where multiple `Set-Cookie` headers are incorrectly overwritten, resulting in only the last cookie being set in the response. The proposed solutions involve either using `appendResponseHeader` instead of `setResponseHeader` or using `Array.reduce` to group headers before setting them. The solution needs to be reviewed for potential side effects and then implemented as a pull request.