Coding On “Performance” Trend
Today, we’re going to look at getting setup with a full stack single page application (SPA) implementation of ReactJS + Redux + Bootstrap 4 + ASP.Net Core.
ReactJS was created by Jordan Walke, a software engineer at Facebook.
ReactJS is component based, so only each component on a page needs to be updated. Remember AJAX? …imagine that with a more structured design and you’re halfway there.
Redux is a “predictable state container” - It shares state across all components within an application. Redux has a store, which holds state for the entire application and the data is supplied as properties (this.props).
“Redux 4 has a much smaller footprint because they removed the lodash dependency (package management).”
Redux has three core components - Actions, Reducers, Store.
Reducers - These specify how the state changes in response to an action. Reducers take the Action payload, and apply it to the store. The state is immutable, so a reducer returns a new state with whatever needs to be added, updated or removed.
Store - This holds the state and allows access to the state. The store allows the state to be updated, whilst also registering listeners to keep an eye on the state when it changes in different modules…
…essentially, Redux is quite powerful and extremely useful!
Enter “Bootstrap 4”…
I’m sure you know the Bootstrap story already - A mobile-responsive framework created by a dedicated team at Twitter originally in 2011 in order to maintain consistent implementations during front-end development. Bootstrap 3 was written in LESS, however Bootstrap 4 is written in SASS with the grid system based on REMs. It’s also worth noting that BS4 has a 64% smaller footprint than BS3 too. Bootstrap 4 is what we’ll be using today!
Enter “ASP.Net Core”…
Finally, our server-side framework will be running on ASP.Net Core. I’ll refrain from explaining this here, other than stating that it’s cross-platform and totally awesome!
First of all, you need to be running the latest version of Node on your machine.
Next we’re going to use the relevant reactredux template to create our project, which for this example I’ve called “full-stack-app” (and this name must be entirely lowercase, but we can change it later).
We then need to CD into that directory to see the template files that have been created by our previous terminal statement.
Once in that directory, open the .csproj file in Visual Studio (this generates a solution file). Save all, and close Visual Studio. You can then rename the solution and your .csproj file.
Following this, open the solution in Visual Studio, clean, rebuild. Then find and replace all of the original name (full-stack-app), to the new name (in my case SimonGilbert.Blog). When doing this, be sure to include both full-stack-app and the same name but with underscores i.e. full_stack_app.
Ok, now to upgrade some key packages. First, CD into the ClientApp subdirectory (this folder houses all the UI source code and packages).
Let’s update the JQuery version.
Now the prop-types package also.
Followed by an upgrade to the latest version of React.
…including the React DOM.
And then Reactstrap (we’ll need this for Bootstrap usage later).
Next we need to upgrade Redux to the latest version.
Followed by Redux Thunk.
And finally, NPM audit fix…..to fix any issues that have occurred along the way (although some of the dependency errors can indeed be ignored).
Reviewing Our Changes
If you now open the solution and navigate to the packages.json file, you should see something similar to this -
Running Our Application
Run the application as normal from Visual Studio, and you should see something similar to the following -
…Result! Now head to the “Fetch data” tab which will load a series of weather forecast data from the server-side. If you now navigate o the controllers folder in Visual Studio, you’ll see the ASP.Net Core Web Api code endpoint that Redux is interacting with via ReactJS.