AI Prompts for Resolving Module System Conflicts

Please scan the open files in the project and identify all instances where both 'require' and 'import' statements are used within the same file. For each instance, provide the corresponding line numbers and file names. Additionally, summarize the potential implications of using mixed import styles in the codebase and suggest best practices for maintaining consistency in module imports. Format the output as a detailed report.

Examine the package.json file in the current project and determine whether it specifies 'type': 'module'. If it does, explain the significance of this setting in relation to how JavaScript modules are handled in the project. Additionally, discuss the implications of using 'module' versus 'commonjs' for module loading, and provide examples of how this affects the import and export syntax in the codebase. Please present your findings in a clear and structured format.

Identify all files in the project that utilize 'module.exports' or 'require'. For each file, provide a brief summary that includes the purpose of the module, how it interacts with other parts of the codebase, and any relevant dependencies or relationships. Additionally, highlight any patterns or common practices observed in the usage of CommonJS within these files. Format the output as a structured report with file names as headings and the summaries below each heading.

Please analyze the codebase and identify all files that utilize 'import' or 'export' statements for ES module usage. For each file, provide the line numbers where these statements occur and highlight any patterns or trends you observe in their usage. Additionally, summarize the implications of these patterns on the overall module system and suggest any potential improvements or refactoring opportunities based on your findings.

Please analyze the current open files in my project for any import-related errors or warnings. Provide a detailed summary of the identified issues, including the specific files and lines where the errors occur. Additionally, suggest possible causes for these import errors, considering factors such as module paths, dependencies, and version compatibility. Format your response as a structured report with clear headings for each issue and its corresponding suggestions.

Please provide a detailed, step-by-step guide for converting files from CommonJS to ES modules. For each file, include the specific changes needed, such as how to replace `require` statements with `import` statements and how to adjust `module.exports` to `export`. Additionally, include code snippets that illustrate each step clearly, and explain any potential issues that may arise during the conversion process, along with solutions. Ensure that the guide is comprehensive enough for someone with basic JavaScript knowledge to follow easily.

Identify the files in my project where 'require' statements are used and suggest the correct 'import' statements to replace them. For each file, provide a brief explanation of the changes made and examples of the new import statements. Additionally, include any necessary adjustments to ensure compatibility with ES6 module syntax. Format your response clearly, with each file's changes listed separately.

Please provide a detailed guide on how to modify the export syntax in JavaScript files. Specifically, demonstrate how to change 'module.exports' to 'export default' or named exports. Include examples of both types of exports, and outline the steps needed to identify the relevant files that require modification. Additionally, explain any potential issues that may arise during this process and how to resolve them.

Please analyze the provided package.json file. If it does not specify 'type': 'module', suggest the necessary changes to include this specification. Explain the impact of these changes on the module system, including how it affects the way modules are imported and exported in the code. Additionally, provide examples of how to correctly structure the imports and exports in both CommonJS and ES module formats to illustrate the differences.

Please analyze the provided code files that utilize both CommonJS and ES module syntax. Recommend a consistent module system approach to adopt throughout the codebase, explaining the advantages of your chosen method. After that, refactor the code to ensure it adheres to the selected module system, providing clear comments on the changes made and any potential impacts on functionality. Ensure the refactored code maintains the original behavior while improving clarity and consistency.

Please execute all existing tests related to module imports and exports in my project. After running the tests, provide a detailed report on any failures, including the specific causes of each failure. Additionally, suggest potential solutions or fixes for the identified issues. Ensure that the report is structured clearly, highlighting the test names, results, and any relevant error messages.

Please re-scan the codebase for any import or export errors. Provide a detailed report of any issues found, including the specific files and lines where the errors occur. Additionally, confirm that there are no remaining issues and summarize the overall status of the codebase after the scan. If errors are found, suggest potential fixes or improvements to resolve them.

Please review the package.json configuration for [PROJECT NAME] and validate that it aligns with the intended module system, which is [MODULE SYSTEM, E.G., COMMONJS, ES MODULES]. Check for any discrepancies or errors in the configuration, including dependencies, scripts, and any relevant fields. Provide a summary of your findings, highlighting any issues that need to be addressed and recommendations for corrections if necessary.

Please review all project files and confirm that they consistently use the same module system. Identify any discrepancies or inconsistencies in module usage across the files. Provide a detailed summary of your findings, including which files adhere to the chosen module system and which do not, along with recommendations for correcting any inconsistencies. Additionally, include any potential impacts of these discrepancies on the overall project functionality.

Please analyze the codebase for any remaining inconsistencies in module usage. Identify specific areas where inconsistencies exist and provide detailed explanations for each issue found. Additionally, confirm whether all previously identified issues have been resolved, and if not, outline the unresolved problems with suggestions for how to address them. Present your findings in a structured report format, including sections for inconsistencies, resolutions, and recommendations.

Draft a rule for a CLAUDE.md file that specifies the requirement for using a single module system throughout the project. The rule should clearly outline the reasons for this mandate, including benefits such as consistency, maintainability, and ease of collaboration. Include specific examples of acceptable module systems and any exceptions to the rule, if applicable. Format the rule in a way that is easy to read and understand, and ensure it can be easily referenced by all team members.

Please provide a standard comment template that can be added at the top of each code file to indicate the module system being used. The comment should include the following elements: the name of the module system (e.g., CommonJS, ES Modules), a brief description of its purpose, and any relevant version information. Ensure the comment is formatted in a way that is clear and easy to read, and provide an example of how it should look when implemented in a code file.

Create a comprehensive checklist for developers to follow when adding new files to ensure consistency in the module system. The checklist should include steps such as verifying the naming conventions for files and modules, ensuring proper import/export statements are used, checking for adherence to the project's coding standards, and confirming that all dependencies are correctly documented. Additionally, include a section for reviewing any related documentation updates that may be necessary. Format the checklist in a clear, easy-to-follow layout with bullet points for each item.

Propose a detailed set of naming conventions for files and directories that align with the [MODULE SYSTEM] being used in my project. Include guidelines for naming structure, such as using lowercase letters, underscores, or hyphens, and provide examples of how to name different types of files (e.g., modules, components, utilities). Additionally, explain the rationale behind these conventions and how they can improve code organization and readability. Format your response as a structured document with headings for each category of naming convention.

Please recommend a detailed script or tool that can automatically check for module system consistency during development. The solution should include specific features such as identifying mismatched module types, providing clear error messages, and offering suggestions for corrections. Additionally, outline how this tool can be integrated into a typical development workflow and any prerequisites needed for setup. Include examples of scenarios where this tool would be particularly beneficial, and suggest best practices for maintaining module consistency throughout the project lifecycle.