Navigation History Made Easy in React and Redux

⚛ Navigation history made easy!

A simple, lightweight library for managing navigation history in React and Redux.

Used in production by Utilmond. Check it out!

👌 Have any requests?

For any requests such as new features, backwards compatibility with react-router 5, other routing libraries or environments such as Cordova please open a GitHub issue.

Some of them are already implemented and will be incrementally added.

If you are in a rush though please open an issue, this way we can prioritize correspondingly :)

✨ Features

📜 Saves all routing history in store and offers selectors for easy access

🌲 History is persisted even after reloading the page

💪 Force current route to re-render capability

⏭️ Skipping screens capability out of the box just by passing a flag when navigating

👀 Everything you need to know about your navigation state and history directly in your favorite developer tools

 
📤 Installation

npm install react-redux-history react react-redux react-router history

🔗 Setup

Step 1)

Create a history object:

// store.js
import { createBrowserHistory } from 'history'

export const history = createBrowserHistory() // export this as we will need it later

Step 2)

Pass the history object as an argument to configureRouterHistory. The returned reducer and middleware will be used to connect to the store.

// store.js
import { configureRouterHistory } from 'react-router-redux-history'

const { routerReducer, routerMiddleware } = configureRouterHistory(history)

Step 3)

Add the reducer and middleware to your store. If you are using Redux Toolkit it might look something like this:

// store.js
const store = configureStore({
  reducer: combineReducers({
    // ...other reducers
    router: routerReducer
  }),
  middleware: (getDefaultMiddleware) => getDefaultMiddleware()
    // ...other middleware
    .prepend(routerMiddleware)
});

export default store

Step 4)

Lastly, add either <LocationListener history={history} /> or useLocationListener(history) somewhere at the root of your app.

Only use one of the approaches! They are only exported like this for flexibility :)

// App.tsx
import { useLocationListener, LocationListener } from 'react-redux-history'
import { history } from 'src/store'

const App = () => {
  useLocationListener(history) // Use either this or the component below, not both!
  
  return (
    <>
      ...
      <LocationListener history={history} />
      ...
    </>
  )
}

Note: the history object provided to configureRouterHistory and useLocationListener / LocationListener must be the same history object !

⏭️ Skip back / forward

By setting a skipBack / skipForward flag on a specific route the user will be automatically skipped over certain routes.

history.push({
  pathname: 'page_5',
  state: { skipBack: 4 }
});

In this example, every time the user will try to go back from page_5 he will be skipped back 4 pages, reaching page_1. The same behaviour will apply when going forward from page_1, the user will be skipped forward to page_5.

Note: Due to the restrictive nature of browser navigation, back or forward actions cannot be stopped. That means that in the previous example the user will actually reach page_4 before being redirected to page_1. If there is conflicting logic (such as extra redirects) in page_4, it will be fired before the middleware manages to completely skip all screens. In order to get past this issue we can use the isSkipping flag to, for instance, not render the component tree while skipping. You can find a selector for this in the selectors section.

💪 Force current route to re-render

Sometimes you might want to force the current route to re-render, a behaviour which is not possible out of the box with react-router.

This can be achieved by selecting the forceRender state in the component you wish to re-render. Then simply 're-navigate' to the route while passing forceRender: {} in the state object.

The forceRender flag can also be used as a dependency in order to re-trigger effects.

🌲 Persistent history

History is persisted even after page refresh by using local storage to save the state on page hide.

🚦 Selectors for easy access

There are also a few useful selectors for easy access:

• selectAction
• selectIsSkipping
• selectForceRender
• selectLocationHistory
• selectCurrentIndex
• selectCurrentLocation
• selectCurrentLocationState
• selectPreviousLocation
• selectNextLocation

Huge thanks going to Utilmond team for making this possible! 🍻

---

Download details:

Author: fum4
Source code: https://github.com/fum4/react-redux-history

License: MIT license

#react-native #redux 

What is GEEK

Buddha Community

How native is React Native? | React Native vs Native App Development

If you are undertaking a mobile app development for your start-up or enterprise, you are likely wondering whether to use React Native. As a popular development framework, React Native helps you to develop near-native mobile apps. However, you are probably also wondering how close you can get to a native app by using React Native. How native is React Native?

In the article, we discuss the similarities between native mobile development and development using React Native. We also touch upon where they differ and how to bridge the gaps. Read on.

A brief introduction to React Native

Let’s briefly set the context first. We will briefly touch upon what React Native is and how it differs from earlier hybrid frameworks.

React Native is a popular JavaScript framework that Facebook has created. You can use this open-source framework to code natively rendering Android and iOS mobile apps. You can use it to develop web apps too.

Facebook has developed React Native based on React, its JavaScript library. The first release of React Native came in March 2015. At the time of writing this article, the latest stable release of React Native is 0.62.0, and it was released in March 2020.

Although relatively new, React Native has acquired a high degree of popularity. The “Stack Overflow Developer Survey 2019” report identifies it as the 8th most loved framework. Facebook, Walmart, and Bloomberg are some of the top companies that use React Native.

The popularity of React Native comes from its advantages. Some of its advantages are as follows:

• Performance: It delivers optimal performance.
• Cross-platform development: You can develop both Android and iOS apps with it. The reuse of code expedites development and reduces costs.
• UI design: React Native enables you to design simple and responsive UI for your mobile app.
• 3rd party plugins: This framework supports 3rd party plugins.
• Developer community: A vibrant community of developers support React Native.

Why React Native is fundamentally different from earlier hybrid frameworks

Are you wondering whether React Native is just another of those hybrid frameworks like Ionic or Cordova? It’s not! React Native is fundamentally different from these earlier hybrid frameworks.

React Native is very close to native. Consider the following aspects as described on the React Native website:

• Access to many native platforms features: The primitives of React Native render to native platform UI. This means that your React Native app will use many native platform APIs as native apps would do.
• Near-native user experience: React Native provides several native components, and these are platform agnostic.
• The ease of accessing native APIs: React Native uses a declarative UI paradigm. This enables React Native to interact easily with native platform APIs since React Native wraps existing native code.

Due to these factors, React Native offers many more advantages compared to those earlier hybrid frameworks. We now review them.

#android app #frontend #ios app #mobile app development #benefits of react native #is react native good for mobile app development #native vs #pros and cons of react native #react mobile development #react native development #react native experience #react native framework #react native ios vs android #react native pros and cons #react native vs android #react native vs native #react native vs native performance #react vs native #why react native #why use react native

Reduce Redux Boilerplate Code with Redux-Actions

Redux has become one of the most popular libraries in front-end development since it was introduced by Dan Abramov and Andrew Clark in 2015. They designed it as the successor for Flux, with the support of some developer tools and a few more concepts embedded in it.

Flux is a fancy name for observer pattern further modified to support React. Both Flux and Redux consist of similar concepts like Store, Actions (events in the application). In other words, Flux is a simple JavaScript object but with some middleware like redux-thunk. It can be a function or a promise for Redux. However, Redux is a single source of truth with concepts like immutability, which improve performance. It is one of the main reasons for Redux to dominate in State Management.

Flux vs Redux comparison source: enappd.com

Despite its advantages, some developers have found it rather challenging to deal with Redux due to the amount of boilerplate code introduced with it. And the complexity of the code seems to be another reason for the difficulty.

In this article, we will look at how to reduce the boilerplate code brought about by Actions and Reducers using Redux-Actions

#react-redux-boilerplate #react-redux #react #react-actions #redux

Himalayausa Clone using React JS and Redux

Inspired from Himalayausa.com

Project-code: closed-birthday-4512

Tech Stack Used

#React.js

#Redux

#Chakra-UI

#React Slick

#JavaScript

#HTML

#CSS

#Heroku

#Versel

#NPM

Deploy link:- Versal

This website was originally inspired from Himalayausa.com Our Team made Tremendus efforts and build this website within 5 consicutive days. We used React.js library for the UI part and used REDUX store for maintaing the states of the components. We used Heroku server API for getting the Mock Data and used Versel to deploy.

sneak peeks of the project...

Landing page...

Shop By Category ...

Best Seller ...

Navbar ...

Footer ...

About Page ...

Login page ...

Signup page ...

product page ...

Single Product ...

Cart page ...

Checkout page ...

Main Contributors

#Anurag Dinkar Pawar GitHub

#Veena Sahu GitHub

#Narayan Chatalwar GitHub

#SHILAJIT PAUL GitHub

#Govind Lakhotiya GitHub

---

Author: AnuragPawar-132
Source code: https://github.com/AnuragPawar-132/closed-birthday-4512

#react #javascript #Redux 

Build a simple React Native Pokemon app with React-Navigation

As we start learning new technologies we want to start building something or work on a simple project to get a better understanding of the technology. So, let’s build this simple app.
For this app, we will be using PokeApi to get our pokemon data, and also we will be using Hooks. I am using pokemondb for pokemon sprites. It’s just a personal preference you can use whatever you want.

#react-native #react-native-app #react-navigation #react-native-development #react

Accessing Redux from Components In React & React Native

How to set up a basic version of Redux in your React or React Native application. To make things clearer, I based my setup on my event application, where users create events that other users attend. We generated the action creators, reducers, and Redux store, and wrapped the application in a provider. Today I’ll finish the loop and talk about how to access the Redux store in your application using both class and functional components. The provider we added to the root component provides the store to all the components in your application. Therefore, we will just look at how to access the store from an individual component.

#react-redux #redux #hooks #react #react-native