Question regarding web SafeAreaProvider `View` usage

[crutchcorn]

In this file, we have a View:

https://github.com/AppAndFlow/react-native-safe-area-context/blob/main/src/NativeSafeAreaProvider.web.tsx#L63

However, this was causing headaches with a web project of mine, seeing as the safe area context is provided at the root of a screen via ExpoRoot:

https://github.com/expo/expo/blob/fcebecf0d92682f81b50c7f0f1620f8ef9e4ebcb/packages/expo-router/src/ExpoRoot.tsx#L66-L72

And ultimately caused headaches in debugging a web app of mine:

https://x.com/crutchcorn/status/1930061117008519445

I don't see a reason why we'd need this View on web. Could we simply replace it with a Fragment instead? I'd be happy to make a PR for this

[hirbod]

I think the best way is to wrap with a Fragment when no style prop is passed. Otherwise, there’s really no need to wrap it in a View.

[janicduplessis]

I think it was mostly for consistency with native where it has to be a View. I am ok with @hirbod solution if you want to open a PR it would be great!

[satya164]

@janicduplessis fyi the provider works as a wrapper view in native stack on web. changing it to a fragment will most likely break things. it can also break things for people using the library in other scenarios. if you're changing to a fragment then please make it do so only via a prop.

[janicduplessis]

I agree, we can add an undocumented unstable_disableViewOnWeb or something like that. We can re-evaluate in the next major.