feat: Support ☯️

[MounirDhahri]

#hackathon

Description

☯️☯️☯️☯️

PR Checklist

• I have tested my changes on iOS and Android.
• I hid my changes behind a feature flag, or they don't need one.
• I have included screenshots or videos, or I have not changed the UI.
• I have added tests, or my changes don't require any.
• I added an app state migration, or my changes do not require one.
• I have documented any follow-up work that this PR will require, or it does not require any.
• I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

• I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates

Changelog updates

Cross-platform user-facing changes

• add dark mode - mounir

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

[ArtsyOpenSource]

This PR contains the following changes:

• Cross-platform user-facing changes (add dark mode - mounir - MounirDhahri)

Generated by 🚫 dangerJS against 1d57fef

[gkartalis]

lets keep this out of package json ;P

[MounirDhahri]

I was going to raise this actually. It's true that it's not used unless one is trying to use code-push, I wonder though if it's really worth it to remove it since it's anyway a dev dependency and it won't affect users but it will slow us down from create code-push canaries

[gkartalis]

this was the reason why it was removed as a dev dependency in the first place #10767

[MounirDhahri]

Thanks for raising that, although it's not a dev dependency, I feel like it's useful to have it there. Currently, I am making many code-push releases and adjusting my code often and testing again.
However each time I want to commit some code, I had to be careful not to commit yarn.lock and package.json after creating a beta.

I am fine with keeping on doing that but I don't see any harm in adding it again.