Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: prevent Require cycles warning #2410

Merged
merged 1 commit into from
Oct 16, 2024
Merged

Conversation

alduzy
Copy link
Member

@alduzy alduzy commented Oct 16, 2024

Description

This PR fixes require cycles warning caused by importing from react-native-screens in a react-native-screens module by changing the imports to relative.

Fixes #2408 .

Changes

  • changed imports to relative

Test code and steps to reproduce

Checklist

  • Ensured that CI passes

@alduzy alduzy changed the title fix: prevent require cycles warning fix: prevent Require cycles warning Oct 16, 2024
Copy link
Member

@kkafar kkafar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should be good here.

One thing we might wanna do, as mentioned by @WoLewicki is to test the lib in external fresh app. After we've done that I think we're good to go. Thank you!

@alduzy alduzy merged commit d5197b6 into main Oct 16, 2024
3 checks passed
@alduzy alduzy deleted the @alduzy/require-cycles-fix branch October 16, 2024 17:56
alduzy added a commit that referenced this pull request Oct 31, 2024
This PR fixes `require cycles` warning caused by importing from
`react-native-screens` in a `react-native-screens` module by changing
the imports to relative.

Fixes #2408  .

- changed imports to relative

<!--

Here you can add screenshots / GIFs documenting your change.

You can add before / after section if you're changing some behavior.

-->

<!--
Please include code that can be used to test this change and short
description how this example should work.
This snippet should be as minimal as possible and ready to be pasted
into editor (don't exclude exports or remove "not important" parts of
reproduction example)
-->

- [x] Ensured that CI passes
alduzy added a commit that referenced this pull request Oct 31, 2024
This PR fixes `require cycles` warning caused by importing from
`react-native-screens` in a `react-native-screens` module by changing
the imports to relative.

Fixes #2408  .

- changed imports to relative

<!--

Here you can add screenshots / GIFs documenting your change.

You can add before / after section if you're changing some behavior.

-->

<!--
Please include code that can be used to test this change and short
description how this example should work.
This snippet should be as minimal as possible and ready to be pasted
into editor (don't exclude exports or remove "not important" parts of
reproduction example)
-->

- [x] Ensured that CI passes

(cherry picked from commit d5197b6)
alduzy added a commit that referenced this pull request Oct 31, 2024
This is a #2410 cherry-pick from main. This PR aims to bring the fix to
v3 as well.

## Description

This PR fixes `require cycles` warning caused by importing from
`react-native-screens` in a `react-native-screens` module by changing
the imports to relative. Additionally it fixes an
[issue](#2302)
with react-compiler in expo projects.

Fixes #2408  #2302.

## Checklist

- [x] Ensured that CI passes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Require cycles break Metro import support
4 participants