mackentoch / react-redux-nextjs-bootstrap-pwa-starter

a progressive web app starter with next js redux + redux-persist + bootstrap

PWA: Next JS + Redux + Redux persist + redux-devtools-extension + Bootstrap starter

A progressive web app starter with NextJS, redux and bootstrap

Lighthouse tests

• v0.1.1 a bit better for not that much efforts. Performance score would be far better without using bootstrap (actully fetched from https://maxcdn.bootstrapcdn.com)

• v0.0.1 (first version: with no optimizations!) pretty nice for an out of the box starting PWA starter!

Detailed Content

Front:

• Next js (9.x+ github 🔗)
• React JS (16.8.x+ - github 🔗)
• redux (as your application grows managing state will be a serious concern, save pain with Redux)
• redux-persist 5.x (simplifies your NextJS state share between pages github 🔗)
• localForage
• react-redux (Redux is not specific to ReactJS, you could easily use it with Angular2 for instance)
• redux-thunk (simple and does the job)
• next-redux-wrapper
• redux-devtools-extension (github 🔗)
• reactstrap (github 🔗)
• axios (github 🔗 Why: simple, complete, isomorphic ...)

Tool chain:

• Next js (9.x+ github 🔗)
• Babel 7+ (custom babel)
• Flow JS types

fav icon:

• favicons generated by realfavicongenerator

Usage

IMPORTANT: Next JS when redux connected

• you are forced to connect each page (even if you don't need redux in that page) with withRedux from next-redux-wrapper (see page1 as an example).
• each sub component you may want to connect should be connected by usual connect from redux (see Header component as an example)

IMPORTANT: use Layout component on each Page:

• Layout is the Layout (better to my mind than using _document) of each page
• Layout component will register the service worker (registering an already registered service worker is no effect but ensures it will register at any page user would enter the application)

Install

yarn install

Scripts

run dev with hot reload

Clone this repository, then install dependencies:

yarn run start

build dev bundle

yarn run build

start dev (no hot reload)

NOTE: ensure you built first before starting

yarn run start

Donate

Do you use & ❤️ react-redux-nextjs-bootstrap-pwa-starter but you don’t find a way to show some love? If yes, please consider donating to support this project. Otherwise, no worries, regardless of whether there is support or not, I will keep maintaining this project. Still, if you buy me a cup of coffee I would be more than happy though 😄

LICENSE

The MIT License (MIT)

Copyright (c) 2019 Erwan DATIN

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

react-redux-nextjs-bootstrap-pwa-starter's Issues

getting an error of setClientState not defined.

HI there... First of all thank by the plugin.
I'm trying to implement this feature in Next js

And I have this code...
_app.js

import { Provider } from "react-redux";
import { appWithTranslation } from "../../i18n";
import withRedux from "next-redux-wrapper";
import { makeStore } from "../lib/redux";
import { PersistGate } from "redux-persist/integration/react";
export default withRedux(makeStore, { debug: true })(appWithTranslation(MyApp))
and in page/index.js I have

export default connect(
(state) => state,
{setClientState}
)(({fromClient, setClientState}))(withNamespaces('landing')(Index))

but IM getting an error of setClientState not defined.

Can you help me, please?

Thanks in advance
Carlos Vieira

Error: Cannot find module 'E:\ReactNative\PWA-RN\react-redux-nextjs-bootstrap-pwa-starter\server.index.js'

Error: Cannot find module 'E:\ReactNative\PWA-RN\react-redux-nextjs-bootstrap-pwa-starter\server.index.js'

Error: Cannot find module 'E:\ReactNative\PWA-RN\react-redux-nextjs-bootstrap-pwa-starter\server.index.js'

should be lifecycle :)

react-redux-nextjs-bootstrap-pwa-starter/pages/login.js

Line 58 in 7aa27f9

// #region component lifeculcle methods

Hi, how to add hash version for chunk file (clear browser cache old js file) when build

ISSUES TEMPLATE

Version

1.2.0

Node JS

v7.x | v8.X

Browser

Chrome 64.x | Safari 11.x

OS version

macOS | windows 10 | linux Ubuntu...

Steps to reproduce

1. explantion 1...

2. explantion 2...

3. explantion 3...

Expected behavior

What should happen

Actual behavior

What is happening

Woefully outdated

This boilerplate is woefully outdated, I was really hopeful in finding it but then discovered the material UI, react and other versions were very old (by years).

Any chance you have a modern version of this lying around?

npm install fails in npm 7

ISSUES TEMPLATE

Node JS

v15.1.0

NPM - 7.0.6

OS version

macOS

Steps to reproduce

1. Clone the repo

2. Run npm install

npm install

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"^5.12.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@">=6.0.0" from [email protected]
npm ERR! node_modules/eslint-plugin-flowtype
npm ERR!   dev eslint-plugin-flowtype@"^3.2.1" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /Users/rmkanda/.npm/eresolve-report.txt for a full report.