Research
Security News
Quasar RAT Disguised as an npm Package for Detecting Vulnerabilities in Ethereum Smart Contracts
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
đ¨ This is still in development.
A dead simple, responsive design system for Expo / React Native Web. Heavily inspired by React's theme-ui
.
<Text
sx={{
fontSize: [14, 16, 20], // 14 on mobile, 16 on tablet, 20 on desktop
color: ['primary', null, 'accent'], // `primary` on mobile & tablet, `accent` on desktop
}}
>
Responsive font size?? đ¤¯
</Text>
Build once, deploy everywhere, is a great philosophy made possible by Expo Web/React Native Web. A large impediment is responsive design.
React Native doesn't have media queries for styles, and trying to micmick it with JS turns into useState
hell with a ton of conditionals (as you'll see below.)
While React Native has some nice component libraries, it lacks responsive styles that respond to theme changes.
No longer. The goal of this library is to let you go from idea -> universal, themed styles without much effort.
There is no shortage of discussions about what responsive design should look like in React Native. After trying many, many different ways, I'm convinced this is the answer.
yarn add @nandorojo/dripsy
# or
npm i @nandorojo/dripsy
Technically, you don't have to do anything else!
However, you'll likely want to create a custom theme.
Wrap your entire app with the ThemeProvider
, and pass it a theme
object. Make sure you create your theme outside of the component to avoid re-renders.
If you're using Next.js, this goes in pages/_app.js
.
App.js
import { ThemeProvider } from '@nandorojo/dripsy';
const theme = {
colors: {
text: '#000',
background: '#fff',
primary: 'tomato',
},
fonts: {
body: 'system-ui, sans-serif',
heading: '"Avenir Next", sans-serif',
},
spacing: [10, 12, 14],
};
export default function App() {
return (
<ThemeProvider theme={theme}>
{/* Your app code goes here! */}
</ThemeProvider>
);
}
Follow the docs from theme-ui
to see how to theme your app â we use the same API as them.
My personal preference is to have the entire theme object in one file.
All theme values are optional. You don't have to use them if you don't want.
If you're using the expo + next.js integration, there are a few extra steps.
1. Install dependencies
yarn add next-compose-plugins next-transpile-modules
2. Edit your next.config.js
file to look like this:
const withPlugins = require('next-compose-plugins');
const withTM = require('next-transpile-modules')([
'@nandorojo/dripsy',
// you can add other packages here that need transpiling
]);
const { withExpo } = require('@expo/next-adapter');
module.exports = withPlugins(
[withTM],
withExpo({
projectRoot: __dirname,
})
);
3. (Optional) add InitializeColorMode
to pages/_document.js
If you're using a color mode (such as dark mode) in your app, you'll probably want to add InitializeColorMode
to avoid a flash of unstyled text.
Just import InitializeColorMode
, and put it in at the top of your body
tag in pages/_document.js
.
Your pages/_document.js
should look something like this.
That's it! Btw, if you're using Expo + Next.js, check out my library, expo-next-react-navigation.
export default {
colors: {
text: '#000',
background: '#fff',
primary: 'tomato',
},
spacing: [10, 12, 14],
};
<Text
sx={{
color: 'primary',
padding: [1, 3], // [10px, 14px] from theme!
}}
>
Themed color!
</Text>
Todo: make the theme values show up in TS types for intelliesense.
This is what it took to make one responsive style without Dripsy...
import { useState } from 'react';
import { View } from 'react-native';
const ResponsiveBox = () => {
const [screenWidth, setScreenWidth] = useState(
Dimensions.get('window').width
);
useEffect(() => {
const onResize = (event) => {
setScreenWidth(event.window.width);
};
Dimensions.addEventListener('change', onResize);
return () => Dimensions.removeEventListener('change', onResize);
}, []);
let width = '100%';
if (screenWidth > 700) {
width = '50%';
}
return <View style={{ width }} />;
};
A big issue with using JS-only breakpoints like that is that it won't work on SSR apps using Expo + Next.js. The "solution" would be to lazy load the component, but then you lose the SEO benefits of Next.js. With Dripsy, SSR works fine!
import { View } from '@nandorojo/dripsy';
const ResponsiveBox = () => {
return <View sx={{ width: ['100%', '50%'] }} />;
};
If you're using the Expo + Next.js integration, you'll have to follow the steps to use styled components with Next.js + Expo.
Change your imports from react-native
to @nandorojo/dripsy
- import { View } from 'react-native'
+ import { View } from '@nandorojo/dripsy'
createThemedComponent
Currently, a bunch of the React Native components are supported. That said, I haven't added them all. If you want to add one, go to src/components
and add one and submit a PR.
Or, you can use the createThemedComponent
function in your own app.
import { createThemedComponent } from '@nandorojo/dripsy';
import { View } from 'react-native'
const CustomView = createThemedComponent(View, {
defaultStyle: {
flex: 1
}
})
First, this library is super inspired by theme-ui
, and uses many of its low-level functions and methodologies.
Practically speaking, this library uses the Dimensions
api on Android & iOS, and uses actual CSS breakpoints on web. The CSS breakpoints are made possible by styled-components
. This means that you get actually-native web breakpoints. That matters, because server-size rendered apps will have startup issues if you use JS-based media queries that require React to rehydrate on when it opens.
On Native, there is nothing too fancy going on. We track the screen width, generate styles based on the current width using a mobile-first approach, and return the regular React Native components. But it just feels like magic!
This is a really new project. I'd love your help and contributions.
Under the hood, this library uses styled-components/native
.
postinstall
script in package.json.MIT
FAQs
đˇ A super-simple responsive design system for React Native Web.
The npm package dripsy receives a total of 2,217 weekly downloads. As such, dripsy popularity was classified as popular.
We found that dripsy demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.