AI Prompts for Resolving Mixed Module Systems

Please provide the exact error message you received regarding module imports in your project. Include the specific line number and the file name where the conflict occurs. Additionally, explain any relevant context about what you were attempting to do when the error was triggered, so I can assist you in diagnosing the issue effectively.

Please provide the full build error message from the build tab that indicates a module system conflict. I will analyze the error to identify the root cause of the issue. Include any relevant context about your project setup, such as the programming language and any specific modules you are using. Format your response clearly so I can assist you effectively.

Please interpret the following instruction regarding module usage: [ORIGINAL INSTRUCTION]. Provide a detailed explanation of your understanding, including any potential ambiguities or areas that may require further clarification. Additionally, outline the key points that you believe are essential for correctly implementing the instruction.

Compare the expected behavior of ES modules with the actual behavior observed in your last build. Include a detailed list of the expected imports alongside the actual output received. Additionally, explain any discrepancies between the expected and actual behaviors, and suggest potential reasons for these differences. Format your response as a table with columns for "Expected Imports," "Actual Output," and "Discrepancies.

Identify the specific module system rule that was violated in the last output regarding the use of CommonJS and ES module syntax. Please quote the exact clause from the documentation that addresses this issue. Additionally, provide a brief explanation of why this rule is important and how it impacts module interoperability. Format your response in a clear and structured manner.

Please modify the import statement in the file [FILENAME] at line [LINE] to use ES module syntax instead of CommonJS. The current import is: [CURRENT IMPORT]. Replace it with the following ES module import: [NEW IMPORT]. Provide a brief explanation of why this change is necessary for compatibility with modern JavaScript standards.

In the file [FILENAME], please revert the export statement at line [LINE] to use CommonJS syntax. The original export was: [CURRENT EXPORT]. Change it to: [NEW EXPORT]. Provide a brief explanation of why this change is necessary and how it impacts the module system. Additionally, include any potential issues that might arise from this change and how to address them.

In the file [FILENAME], review the code to identify all instances of CommonJS require statements. Replace each of these require statements with the appropriate ES module import syntax. Additionally, ensure that all exports in the file are also converted to use ES module export syntax. Provide a summary of the changes made and any potential issues that may arise from this conversion.

Please analyze the project files and enforce a rule that all files must use ES module syntax. Generate a detailed report listing all files that currently use CommonJS syntax, including their file paths and a brief explanation of what changes are necessary to convert them to ES module format. Additionally, suggest best practices for maintaining module format consistency moving forward.

Identify any dependencies in the package.json file that require CommonJS. For each identified dependency, determine if it can be updated to be compatible with ES modules. Provide a list of these dependencies along with specific instructions on how to update them, including any necessary changes to the import statements in the codebase. Format the output as a detailed report with sections for each dependency, including the current import method and the recommended ES module import method.

Please run the build process for the project related to [USE-CASE] and verify that there are no errors associated with module imports. After running the build, provide a detailed output of the build process, including any warnings or messages that may appear. Ensure that the output is formatted clearly for easy review.

Please provide a detailed diff of the changes made to [FILENAME]. Focus specifically on highlighting the modifications related to the module system, and explain how each change impacts the overall functionality. Format the output to clearly distinguish between additions and deletions, and include comments on any potential issues or improvements that could be made.

Please recreate the original scenario that led to the module conflict in [PROGRAM NAME]. Document the steps taken to trigger the error and include any relevant code snippets. After implementing the changes, verify that the same error does not occur and provide a summary of your findings, including any new error messages or issues that arise.

Please test the edge cases for importing modules in different contexts within the [PROGRAMMING LANGUAGE] environment. Identify at least five specific scenarios, such as importing within functions, conditionally importing, or circular imports. For each scenario, confirm that there are no errors and provide a brief explanation of the outcome, including any unexpected behavior or issues encountered.

Please verify the state of the file named [FILENAME] after implementing the changes. Confirm that it accurately reflects the correct module system and does not include any mixed syntax. Provide a summary of your findings, highlighting any discrepancies or issues that need to be addressed.

Please create a system instruction for the project titled 'Module System Enforcement'. The instruction should specify that before any code execution, the system must verify that all imports and exports adhere to ES module syntax. If any CommonJS syntax is detected, the system should halt execution and alert the user with a clear message. Format the instruction as a detailed guideline that can be easily implemented in the project.

Create a conversation starter template for discussing module usage in projects. Begin with the question, "When adding new modules, how can we confirm whether they follow ES module syntax?" Follow up by providing guidance on what to do if they do not adhere to this syntax, including specific steps for converting them to ES modules. Format this as a checklist that can be easily referenced during discussions.

Please add a comment guard at the top of each file to ensure that only ES module syntax is used. The comment should read: '/* Ensure this file uses ES module syntax only. Mixing with CommonJS will cause errors. */'. Confirm that this comment is included in all relevant files to prevent any recurrence of module system errors.

Draft a project convention message regarding the module system for our team. The message should state that all new code must adhere to ES module syntax. Additionally, include a reminder for team members to review existing files for compliance and outline the steps they should take to update any files that do not meet this standard. Ensure the message is clear and emphasizes the importance of maintaining consistency in our codebase.

Please create a self-check request for module compliance in a project. The request should specify that before deployment, the system must run a check for any files using CommonJS syntax. List all identified files that do not comply and provide a message indicating that deployment should be halted until these files are updated to the appropriate module system.