Skip to content

fix: tree-shake away the react-scan require manually if it’s not used #339

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.

Sign up for GitHub

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

Jump to bottom
Merged
natew merged 1 commit into from
Dec 25, 2024
Merged

fix: tree-shake away the react-scan require manually if it’s not used #339

natew merged 1 commit into from
Dec 25, 2024

Conversation

@zetavg
Copy link
Collaborator

@zetavg zetavg commented Dec 25, 2024 •
edited
Loading

A workaround before we have #340.

@railway-app
Copy link

railway-app bot commented Dec 25, 2024

This PR was not deployed automatically as @zetavg does not have access to the Railway project.

In order to get automatic PR deploys, please add @zetavg to your team on Railway.

@zetavg zetavg force-pushed the fix-rn-treeshake-react-scan-2 branch from 8e91a0a to 814b0e2 Compare December 25, 2024 17:27
@natew natew merged commit 032c115 into main Dec 25, 2024
12 checks passed
@natew natew deleted the fix-rn-treeshake-react-scan-2 branch December 25, 2024 17:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@zetavg @natew