20 of the best prompts for identify export changes impacting imports, step by step across 4 stages. Works with ChatGPT, Claude, and Gemini.
20 of the best prompts for identify export changes impacting imports, step by step across 4 stages. Works with ChatGPT, Claude, and Gemini.
Getting Identify Export Changes Impacting Imports right takes more than a single prompt. This 4-stage guide covers Diagnose the Wall, Isolate and Fix, Verify the Resolution, and more, breaking the whole process into focused steps where each prompt builds on the last. The issue arises when Bolt modifies a module's exports without updating the dependent files, leading to broken imports. If left unaddressed, this can cause runtime errors and hinder application functionality. By following this guide, developers can ensure that all module exports are correctly aligned with their imports, preventing future issues. Every prompt is optimized and runs in ChatGPT, Claude, and Gemini.
Check the output logs for any errors related to module imports after recent changes. Look specifically for messages indicating missing or incorrectly referenced exports.
Quote the changed export
Please provide the exact output of the last change made to the module exports in [MODULE NAME]. Identify the specific function or variable that was altered and compare it to the expected export as defined in the project documentation. Format your response to include the altered export, the expected export, and a brief explanation of any discrepancies between the two.
Paste the import statements
Please provide the import statements from the files that are currently failing due to recent changes. I need to analyze these imports to determine which ones are affected and how they connect to the modified exports. Format the output as a list, clearly indicating the file name for each import statement.
State your interpretation of the task
Please provide your interpretation of the original instruction regarding the module exports in the context of the task "bolt-breaking-existing-imports." Explain your understanding in detail, including any potential misunderstandings that could arise and how they might impact the process of diagnosing the wall. Format your response as a structured analysis with clear points for each aspect you identify.
List expected vs. actual exports
Please provide a detailed comparison of the expected exports versus the actual exports following the last change in the system. Include specific details about what the expected exports were, how they were defined, and outline the discrepancies between the expected and actual exports. Format the output in a table with columns for "Expected Exports," "Actual Exports," and "Differences," and provide a brief explanation of the implications of these differences.
Identify violated export rules
Identify the specific rule or pattern regarding module exports that was violated in this instance. Please provide a detailed explanation of the violation, including the exact clause from your project guidelines that outlines the expected behavior for exports. Additionally, suggest potential solutions or adjustments that could be made to align with the guidelines moving forward. Format your response in a clear, structured manner.
Target the specific module where the exports were changed and identify the necessary adjustments to restore proper functionality.
Revert export to original
Please revert the export signature at [MODULE_PATH]:[LINE] to its original form, which is: [PASTE]. Before applying the change, provide me with a diff that highlights the differences between the current export signature and the original one. Ensure that only the export signature is modified, and maintain all other aspects of the function as they are.
Rewrite export with constraints
Rewrite the export for the module located at [MODULE_PATH] to ensure compliance with the defined export constraints. Please provide the original export format and detail the specific changes required to align with the project standards. Additionally, include any relevant examples or explanations to clarify the adjustments made.
Scoped change to imports
Adjust the import statements in [FILE_PATH] to ensure they correctly reference the updated exports from [MODULE_PATH]. Focus on modifying only those import statements that directly relate to the changed exports, and provide a summary of the adjustments made. Format your response to include the original import statement, the modified version, and a brief explanation of why each change was necessary.
Enforce export format
Please review the export format in [MODULE_PATH] and ensure it adheres to the required structure of [EXPECTED_FORMAT]. Identify any discrepancies and make the necessary changes to comply with this format. After making the adjustments, provide a brief summary of the modifications made and any potential impacts on existing imports.
Correct dependencies in imports
Check all dependencies in [MODULE_PATH] and verify that they are correctly imported in the files that reference them. For each file, provide a list of any discrepancies found, including the incorrect imports and the correct versions. Additionally, suggest the necessary changes to fix these discrepancies, ensuring that the imports align with the current structure and requirements of the module.
Confirm that the changes made have resolved the import issues and that the application is functioning as expected.
Run a test on imports
Please run a comprehensive test suite on all files importing from [MODULE_PATH]. Ensure that there are no errors related to missing or incorrect imports following the recent changes. Provide a summary of the test results, highlighting any issues found and recommendations for resolution.
Show diff of changes
Display the differences in code changes made to [MODULE_PATH] and list the affected import files. Provide a detailed comparison that highlights what has been added, modified, or removed. Additionally, ensure that all modifications align with the expected behavior by summarizing how these changes impact the overall functionality.
Replay the original failing scenario
Replay the original scenario that caused the import failures in the application. Confirm that the application functions correctly and does not produce any errors related to module exports. Provide a detailed report of the steps taken during the replay, including any discrepancies observed and how they were resolved.
Check edge case imports
Please identify and analyze any edge case imports related to the [SPECIFIC MODULE OR FUNCTIONALITY] that may regress after the fix. For each edge case, provide a detailed explanation of how it is currently handled and confirm whether it is managed correctly. Additionally, suggest any necessary adjustments or improvements to ensure robust handling of these edge cases moving forward.
Confirm output state
Please verify the output state of the application after implementing the fix for the bolt-breaking-existing-imports use-case. Specifically, check that all components relying on the modified exports are functioning correctly and provide a detailed report on any issues found. Include information on which components are affected, the nature of any problems, and suggestions for further action if necessary.
Create artefacts that will help prevent similar issues with module exports in the future.
Export Consistency Check Prompt
Please provide a detailed session-opening constraint for the project titled "Export Consistency Check." Use the following format: 'Before any changes to module exports, verify that all dependent imports are updated accordingly. If any import is outdated, stop and notify the developer before continuing.' Ensure that the constraint is clear and concise, and explain the importance of maintaining import consistency to prevent potential issues in the codebase.
Import Validation Template
Please create a template for validating imports after any module export changes. The template should follow this format: 'After modifying exports in [MODULE_PATH], check that all imports in [IMPORT_FILES] are updated. If any imports are not updated, list them and provide suggested corrections for each one.' Ensure the template is clear and easy to follow for developers.
Module Export Specification Message
Draft a project specification message that outlines the rules for module exports. Ensure to include the following details: state that all module exports must be documented in [DOCUMENTATION_PATH], and specify that any changes to the exports must trigger a review of all related imports. Additionally, clarify the process for updating the documentation and the timeline for reviews to ensure compliance.
Naming Convention for Exports
Establish a naming convention for exports that ensures clarity and consistency. Use this format: 'All exports in [MODULE_PATH] must follow the pattern [PATTERN]. This will help prevent import mismatches.'
Self-Check for Export Changes
Please create a self-check request for an agent to execute whenever exports are modified. The request should include the following instructions: 'Before finalizing any export changes, ensure that all related imports are updated. If any discrepancies are identified, immediately alert the developer with a detailed report of the issues found.' Format the output as a checklist for easy reference.
Changing a module's exports can lead to broken imports in other files that rely on the original structure. Bolt may not automatically update these imports, causing runtime errors.
You can check the output logs for errors related to missing imports after modifying module exports. Bolt will typically indicate which imports are failing during runtime.
Bolt does not automatically fix import issues after export changes. It requires manual verification to ensure all imports are correctly aligned with the new exports.
Before changing exports, ensure you review all dependent files for their import statements. This will help prevent broken references when the exports are modified.
To prevent future export issues, establish clear guidelines for module exports and imports. Ensure that any changes to exports are accompanied by a review of all related imports.
AI Prompts for Identify Causes of Test Failures
Test failures can arise unexpectedly after changes, leading to confusion and wasted debugging time.
See promptsAI Prompts for Prevent Module Export Conflicts
When a module's exports change without updating the importing files, it can lead to runtime errors and broken functionality.
See promptsAI Prompts for Preventing Module Export Breakages
When Cursor changes a module's exports without updating dependent files, it causes import errors and breaks the build.
See prompts