ReactNative compatibility about styled-components

[geelen]

What might that look like? styled(x)y:z;`` for some x y and z

[mxstbr]

Same API, except with ReactNative primitives?

styled.View`
border: 1px solid red;
`;

(see here for more info on RN styling)

[geelen]

From discussion, the idea is to provide the same API at two endpoints

import styled, { css, ... } from 'styled-components'
import styled, { css, ... } from 'styled-components/native'

The difference is that the DOM one supports nesting, media queries etc, and generates className. The native one doesn't and generates a styles object. We could even not call it the 'native' endpoint but 'inline' instead, since that's all it's doing...

[geelen]

Just thinking about this, if we are going to supply styled.View (as apposed to only allowing styled(View) that means our project is going to depend on react-native just so we can match up our imported symbols. Is there any way around that, or is that not too much of a problem?

[mxstbr]

Is there any way around that, or is that not too much of a problem?

Why not make it a peerDep?

Also, I've been thinking about this – we could not only have /native, but also /choo, /glimmer, even /dom. What if we returned a representation of a generic component from styled calls, and then we could (or collaborators could contribute) more adapters for this thing?

[geelen]

Yeah right that's what peerDeps are for, right? I just thought they would complain if they were unfulfilled, so every time you npm i you get a warning that you're missing react-native?

[mxstbr]

I just thought they would complain if they were unfulfilled, so every time you npm i you get a warning that you're missing react-native?

Ah yeah crap, good point. It's an optionalDependency!

[geelen]

Closing in favour of #53