AI Prompts for Identify Incorrect Export Patterns

Please quote the exact export statement from the file where the error occurs. Analyze the context of the import statements in use to determine whether the export should be a named export or a default export. Provide a brief explanation of your reasoning for the classification based on the import statements.

Please analyze the following import statement from the file that is failing to import the component: [IMPORT STATEMENT]. Determine if it matches the expected export type, either named or default, from the source file: [SOURCE FILE]. Provide a detailed explanation of any discrepancies and suggest how to correct them to ensure successful imports.

Please interpret the export requirements for the component related to the use-case "bolt-wrong-export-pattern." Clearly state whether a named or default export is expected based on the provided context. Include specific details about the component's structure and any relevant factors that influence the export decision. Format your response as a concise summary that outlines your interpretation and reasoning.

Compare the expected export type with the actual export type for the failing component in the context of the bolt-wrong-export-pattern. Clearly detail the expected import statement, including the specific type or structure it anticipates, and contrast this with the actual export being utilized by the component. Present your findings in a structured format, highlighting discrepancies and potential implications for functionality.

Identify the specific export rule or pattern that has been violated regarding export types in the component. Please quote the exact clause from the documentation that specifies the expected export format. Additionally, provide a brief explanation of how the violation impacts the functionality of the component and any potential solutions to correct the issue.

Correct the export statement in [FILE] at line [LINE] to match the expected import type. If a named export is required, please ensure that it is defined correctly as a named export. Provide the corrected export statement along with a brief explanation of why the change is necessary to maintain compatibility with the import.

Rewrite the export statement in [FILE] at line [LINE] to enforce a named export. Ensure that the format follows 'export const [NAME] = ...;' to comply with the import requirements. Provide a brief explanation of why this change is necessary for proper module functionality.

Please modify the export in [FILE] at line [LINE] to ensure it is a named export. After making this change, review all relevant files and update the import statements to reflect the new named export. Provide a summary of the changes made, including the original export statement and the updated import statements in the affected files.

Please review the export statements in the file [FILE] to ensure that they adhere to a consistent format. Identify any components that are not exported as named exports and provide a list of these components. Additionally, suggest the necessary changes to convert any default exports to named exports, ensuring that the overall structure remains coherent and follows best practices.

Review the codebase for all import statements that reference the modified component [COMPONENT NAME]. Update these statements to ensure they correctly reflect the new export type [NEW EXPORT TYPE]. Provide a summary of the changes made, including the original import statements and the updated versions, to prevent any further issues.

Please run the build process for the project and check for any errors related to exports. Specifically, confirm that the previous error regarding the export type, which was identified as [EXPORT ERROR], no longer appears in the output. Provide a summary of any new errors encountered, if applicable, and indicate whether the build was successful or not.

Display the diff of the changes made to [FILE]. Highlight the modifications to the export statement, ensuring they align with the expected import requirements. Additionally, provide a summary of the key differences and any potential implications these changes may have on the overall functionality of the code. Format the output clearly, with sections for the original and modified code snippets.

Reproduce the scenario that previously caused the export error in the application. Verify that the application now functions correctly by testing the same conditions and ensuring that no import-related errors are thrown. Document the steps taken during the reproduction process and the results of the verification, including any error messages encountered or confirmation of successful operation.

Please verify the resolution of edge cases for the component import in different contexts. Test the following scenarios: importing the component as a default export, named export, and within a dynamic import statement. Document any errors encountered, and provide a summary of the results, including which variations worked correctly and any necessary fixes or adjustments.

Please verify the output state of the application after implementing the recent changes. Confirm that the component is functioning as expected by checking for any import errors. Provide a detailed report that includes the current output state, any discrepancies found, and suggestions for resolving any issues identified.

Create a system prompt that enforces the use of named exports for components in this project. The prompt should state: 'Always use named exports for components in this project. If a default export is detected, flag it for review.' Format this as a clear and concise instruction that can be easily copied and pasted into the codebase.

Create a conversation-starter template for verifying code exports before making any changes. The template should include a section for listing all components and specifying whether they use named exports. Additionally, include a subsection for documenting any deviations found from this standard, along with a brief explanation of the impact of these deviations. Format the output as a structured document with headings for 'Components', 'Named Exports', and 'Deviations'.

Draft a project specification message regarding export rules for the project titled [PROJECT NAME]. The message should clearly state: "All components must use named exports. Any default exports will be flagged and require justification." Ensure the wording is formal and suitable for a project documentation context.

Please create a naming convention guideline for component exports. The guideline should specify that components must be named using PascalCase and exported as named exports. Include an example in the format: "export const MyComponent = ...;". Present this information in a clear and concise format that can be easily referenced by developers.

Please create a self-check request for export compliance that includes the following elements: a clear statement reminding team members to check all components for export compliance before deployment, and a specific guideline indicating that no default exports should be present where named exports are required. Format this request as a checklist with bullet points for clarity, ensuring it is easy to follow and implement.