AI Prompts for Resolve Module System Conflicts

Please provide the exact error message related to module imports or exports that you received in the console. Indicate if the message specifically mentions CommonJS or ES modules. Additionally, summarize any relevant context about when the error occurred, such as the code you were trying to run or the specific actions that led to the error. Format your response in a clear, structured manner for easy understanding.

Please analyze the following build error output for module system conflicts: [ERROR OUTPUT]. Identify the specific issues causing the conflict and provide a detailed explanation of the root cause. Additionally, suggest potential solutions or workarounds to resolve the issue effectively. Format your response as a structured report with clear headings for each section.

Please summarize your understanding of the instruction regarding the module system usage in the context of the bolt-wrong-module-system. Include key points such as the intended functionality, any specific requirements or constraints mentioned, and potential areas of confusion that may need clarification. Format your response as a structured outline with bullet points for clarity.

Compare the expected behavior of module imports and exports in the [MODULE SYSTEM] with the actual behavior currently observed. Clearly outline the correct module system's specifications, including how imports and exports should function. Then, detail the discrepancies between the expected and actual behavior, providing examples of each to illustrate the differences. Format your response in a table for clarity, with columns for "Expected Behavior," "Actual Behavior," and "Examples.

Identify and quote the specific rule or constraint regarding module imports and exports that has been violated in the following code snippet: [CODE SNIPPET]. Explain how this violation affects the functionality of the code and suggest a solution to resolve the conflict. Format your response in a clear and structured manner, outlining the rule, the violation, and the proposed fix.

Identify the file that contains an import statement using CommonJS syntax. Convert this import statement to use ES module syntax instead. Provide a detailed comparison by showing the differences between the old CommonJS import and the new ES module import in a clear diff format.

Identify the file containing export statements that mix module systems. Rewrite these statements to ensure they all use a consistent ES module export format. Please provide both the original code snippets and the revised versions, clearly labeled as "Before" and "After.

Identify a specific function in the code that uses the wrong module import style. Change only that function to use the correct ES module import syntax. Please provide the modified code along with a brief explanation of the changes made and why the new import style is preferred.

Review the entire codebase for the use of mixed module formats. Identify all files that do not conform to ES module syntax and create a detailed checklist of these files. Additionally, provide specific recommendations for updating each file to ensure consistency in module format across the codebase.

Identify the dependencies in the [PROJECT NAME] that require CommonJS compatibility. Provide a detailed list of these dependencies along with their current versions and the recommended updates to ensure compatibility with ES modules. Additionally, explain the potential issues that may arise from not updating these dependencies and suggest a timeline for implementing these changes.

Please execute the build command for the [PROJECT NAME] to verify the module system. Ensure that the output confirms a successful build, free from any warnings or errors. After running the test, provide a summary of the results, including any relevant logs or messages that may indicate issues or confirm success.

Please display the diff of the files where changes were made to correct the module system for the use-case 'bolt-wrong-module-system'. Ensure that the output clearly highlights the modifications and reflects a consistent module format. Include a brief explanation of each change and why it was necessary for maintaining consistency.

Re-run the original scenario that caused the module system conflict in the [APPLICATION NAME]. Verify that the scenario executes successfully without any errors related to module imports or exports. Provide a detailed report of the results, including any error messages encountered previously and confirm their resolution.

Please test the edge cases in the application related to module imports. Identify any scenarios that may lead to module-related errors, and provide a detailed report on whether these edge cases function correctly. Include examples of the edge cases tested, the results of each test, and any recommendations for improvements if errors are found.

Verify the output state of the key files affected by the module system changes for the use-case: [USE-CASE NAME]. Please check that each file now reflects the correct module format and functionality. Provide a detailed report listing any discrepancies found, along with suggestions for correcting them, and ensure the report is structured with sections for each file reviewed.

Before executing any code, please verify that all module imports and exports in the provided code snippet are consistently using ES module syntax. If you detect any discrepancies, halt execution and provide a detailed report of the issues found, including the specific lines of code where the inconsistencies occur. Format the output as a list of discrepancies with explanations for each.

Create a conversation-starter template for discussing module import guidelines. The template should include the following points: first, explain the importance of using ES module syntax for all imports. Second, provide a clear instruction on what to do if CommonJS is encountered, emphasizing the need for immediate conversion to ES module syntax. Format this template as a checklist that can be used during code reviews or team discussions.

Draft a project specification message regarding module usage for the project titled [PROJECT NAME]. Clearly state that all modules must adhere to ES module syntax exclusively. Specify that any instances of CommonJS will necessitate a review and refactor process, and outline the steps for how this review will be conducted. Include a timeline for compliance and any resources available for team members to assist with the transition.

Please create a detailed naming convention guideline for module files in the context of the 'bolt-wrong-module-system'. Specify that all module files should be suffixed with '.mjs' to indicate they use ES module syntax. Include the rationale behind this convention, how it helps prevent mixing module types, and any additional best practices for naming files in this system. Format the output as a structured document with headings for each section.

Please create a self-check request for the module imports in the codebase. Before each deployment, the system should run a check to ensure that no CommonJS syntax is present. If any CommonJS syntax is found, generate a detailed report of the findings, including the specific locations and lines of code where the syntax occurs, so that necessary corrections can be made promptly.