I’d like to announce react & react-native community tool, dooboo-cli version 3. Please use 3.2.0 or above.
I know many of you aren’t familiar with dooboo-cli. To explain briefly, this is our community tool that easily creates full-featured boilerplate for react & react-native.
The boilerplate contains below.
- Ability to theme your app with @dooboo-ui/native-theme.
- Typescript
- Navigation with react-navigation or react-router-dom
- Jest with testing library
- Localization
- React hook and so on
If you’ve ever tried yourself to create your own react or react-native boilerplate, you might have felt time-consuming to integrate all the above and even safely. I’ve also felt that. I’ve always wanted to make better and efficient boilerplate that I’ll use every day and I’d also like to validate with others that the boilerplate is worth it. I’ve had worked hard to maintain all the boilerplates I am using these days.
There were few thankful letters in building this cli tool.
We are using dooboo-cli efficiently in our community held in South Korea. It is especially helpful to beginners on how to start react or react-native to walk the right way through the production without digging themselves to mature for a few months.
Lets now download our cli tool if interested.
Now we will see what you can do more other than generating boilerplate.
- You can create
screencomponent orsharedcomponent.
2. You can create navigation component with all samples for navigation.
3. You can create provider component of two types.
- State type
- Reducer type
You can easily distinguish the differences between the two types of providers. First, [State] provider is just passing down the global states to children. Secondly, [Reducer] provider uses useReducer in order to handle middleware more efficiently. We strongly suggest the second one only if you want to manage middleware systematically whereas handling complex logic.
Also, we strongly suggest not to use redux or mobx if you are new to react or react-native. Those helper libraries should be chosen when you have reached the point where you can make a decision on which could be right to go. If you are just the beginner and started using redux and saga, 99% I am sure, you are going on the wrong way which makes developers who will join lately suffer from reading your code (you’ll be lucky when they don’t shoot you 😅).
By using our [Provider] pattern, you can easily, handle global state even with code splitting. If you wrap your component with [Provider] you’ve created, you can use useStateContext elsewhere in child components.
I recommend you to take time with us and make yourself comfortable with our boilerplates. Our work has already proved by a few other startups that it can reach the production level application without making yourself difficult on choosing a few other libraries. Also, we are always opened to talk with many other people on making better starter projects.
Thank you for reading. I hope you to try out for dooboo-cli today 👐.
