The Problem with useImportRestrictions Rule

Oct 13, 2025 by wbrum.org 130 views

Background

In recent times, the use of AI coding tools has become increasingly popular in the development community. These tools, such as Cursor and Cline, aim to enhance the coding experience by providing features like code completion, debugging, and more. However, some developers have reported issues with these tools when used in conjunction with our Biome configuration. The root cause of this problem lies in the useImportRestrictions rule, which is enabled by default in our Biome configuration.

The Problem with useImportRestrictions Rule

The useImportRestrictions rule is designed to prevent unnecessary imports in our codebase. While this rule is beneficial in maintaining a clean and organized codebase, it can sometimes conflict with the functionality of AI coding tools. These tools often rely on importing specific modules or libraries to function correctly. When the useImportRestrictions rule is enabled, it can prevent these tools from importing the necessary modules, leading to compatibility issues.

Proposed Changes

To resolve this issue, we propose disabling the useImportRestrictions rule in our Biome configuration. This change will allow AI coding tools to function correctly, thereby improving the overall developer experience.

Modify Biome Configuration

To disable the useImportRestrictions rule, we need to modify the frontend/packages/configs/biome.jsonc file. The following code snippet shows the changes that need to be made:

  "nursery": {
-   "useImportRestrictions": "error"
+   "useImportRestrictions": "off"
  }

By changing the value of useImportRestrictions from "error" to "off", we are effectively disabling this rule.

Review and Fix Linting Issues

After making this change, we need to review our codebase to identify any linting issues that may have arisen from this change. We should fix any issues that we find to ensure that our codebase remains clean and organized.

Expected Benefits

By disabling the useImportRestrictions rule, we can expect the following benefits:

Better compatibility with AI coding tools: This change will allow AI coding tools to function correctly, thereby improving the overall developer experience.
Improved developer experience: With AI coding tools functioning correctly, developers will be able to leverage these tools more effectively, leading to improved productivity and efficiency.
Reduced friction in the development workflow: By resolving compatibility issues with AI coding tools, we can reduce the friction in our development workflow, making it easier for developers to work on our codebase.

Implementation Notes

To ensure a smooth implementation of this change, we should follow these guidelines:

Make this change in a separate PR: To isolate the configuration change, we should make this change in a separate pull request (PR).
Monitor for unintended consequences: We should closely monitor our codebase for any unintended consequences of disabling this rule.
Update documentation: If we have any references to import restrictions in our documentation, we should update them to reflect this change.

Tasks

To implement this change, we need to complete the following tasks:

Update Biome configuration: We need to update the frontend/packages/configs/biome.jsonc file to disable the useImportRestrictions rule.
Run linter across the codebase: We need to run the linter across our codebase to identify any new warnings or errors that may have arisen from this change.
Fix any issues that arise from the configuration change: We need to fix any issues that we find to ensure that our codebase remains clean and organized.
Test the change with AI coding tools: We need to test the change with AI coding tools to verify improved compatibility.

Conclusion

Q: What is the useImportRestrictions rule in Biome configuration?

A: The useImportRestrictions rule in Biome configuration is designed to prevent unnecessary imports in our codebase. While this rule is beneficial in maintaining a clean and organized codebase, it can sometimes conflict with the functionality of AI coding tools.

Q: Why is the useImportRestrictions rule causing issues with AI coding tools?

A: AI coding tools often rely on importing specific modules or libraries to function correctly. When the useImportRestrictions rule is enabled, it can prevent these tools from importing the necessary modules, leading to compatibility issues.

Q: What are the benefits of disabling the useImportRestrictions rule?

A: By disabling the useImportRestrictions rule, we can expect the following benefits:

Better compatibility with AI coding tools: This change will allow AI coding tools to function correctly, thereby improving the overall developer experience.
Improved developer experience: With AI coding tools functioning correctly, developers will be able to leverage these tools more effectively, leading to improved productivity and efficiency.
Reduced friction in the development workflow: By resolving compatibility issues with AI coding tools, we can reduce the friction in our development workflow, making it easier for developers to work on our codebase.

Q: How do I update the Biome configuration to disable the useImportRestrictions rule?

A: To update the Biome configuration, you need to modify the frontend/packages/configs/biome.jsonc file. The following code snippet shows the changes that need to be made:

  "nursery": {
-   "useImportRestrictions": "error"
+   "useImportRestrictions": "off"
  }

By changing the value of useImportRestrictions from "error" to "off", you are effectively disabling this rule.

Q: What should I do after updating the Biome configuration?

A: After updating the Biome configuration, you should review your codebase to identify any linting issues that may have arisen from this change. You should fix any issues that you find to ensure that your codebase remains clean and organized.

Q: How do I test the change with AI coding tools?

A: To test the change with AI coding tools, you need to run the AI coding tools on your codebase and verify that they are functioning correctly. You should also test the AI coding tools with different scenarios to ensure that they are working as expected.

Q: What are the potential risks of disabling the useImportRestrictions rule?

A: Disabling the useImportRestrictions rule can lead to unnecessary imports in your codebase, which can make it harder to maintain and debug your code. You should closely monitor your codebase for any unintended consequences of disabling this rule.

Q: How do I document the change to disable the useImportRestrictions rule?

A: You should update the documentation to reflect the change to disable the useImportRestrictions rule. This will help other developers understand the change and ensure that they are aware of the potential risks and benefits of this change.

Q: What are the next steps after implementing the change to disable the useImportRestrictions rule?

A: After implementing the change to disable the useImportRestrictions rule, you should continue to monitor your codebase for any unintended consequences of this change. You should also review and update the documentation as needed to reflect the change.