Alternative for babel-plugin-module-resolver

[ETLopes]

Description

The React Native documentation (https://reactnative.dev/docs/typescript) currently references babel-plugin-module-resolver, a library that has been archived and is no longer actively maintained. This raises concerns about the future reliability and support for this tool within the React Native ecosystem.

What is the problem?

The library babel-plugin-module-resolver mentioned in the React Native documentation for handling module aliases has been archived as of June 8, 2023, and is now in read-only mode. This means it will no longer receive updates or support, which could lead to potential issues for developers relying on this tool for their React Native projects.

How can we address it?

It would be beneficial for the React Native documentation to either update the current guidance with a maintained alternative or provide a new solution for managing module aliases. This will ensure that developers have access to reliable and supported tools for their development work.

Why is it important?

Having up-to-date and maintained tools referenced in the official documentation is crucial for developer productivity and the overall health of the React Native ecosystem. Relying on archived or unsupported libraries can lead to development challenges, including compatibility issues, lack of future feature development, and potential security vulnerabilities.

Who needs this?

This change is important for all React Native developers, especially those who are relying on module aliasing in their projects. It is particularly crucial for new learners who are following the official documentation to set up their development environments and build their applications.

When should this happen (use version numbers if needed)?

Given the archived status of babel-plugin-module-resolver, updating the documentation should be considered a high priority. It would be ideal to address this before the next minor or major version release of React Native to ensure that developers have access to the most accurate and reliable information.

[github-actions]

👋 Hey there, it looks like there has been no activity on this issue in the last 90 days. Has the issue been fixed, or does it still require the community attention? This issue will be closed in the next 7 days if no further activity occurs. Thank you for your contributions.

[github-actions]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.