- Changed all class components to functional ones (the
pages/_app.jsandpages/_document.jswere kept as class components, read more here: https://nextjs.org/docs/advanced-features/custom-document) - creativetimofficial/ct-nextjs-argon-dashboard-pro#1 (it also solves the serverless issues as well)
- please check inside
pages/admin/sortable.jsandpages/admin/components.jsto see the solution
- please check inside
- Delete the
src/assets/scss/bootstrapfolder and changed all the bootstrap imports fromsrc/assets/scssfiles to ones fromnode_modules
components/TagsInput/TagsInput.js(it is actually react-tagsinput, but it uses new React API)
- @types/react
- @types/markerclustererplus
- @types/googlemaps
- react-google-maps (We've replace this plugin with Google Maps API Vanilla JS)
- react-tagsinput (we've copied the code from this plugin, and updated it to latest React version)
- [email protected] (so that we can import the styles from node_modules, not a downloaded version)
- [email protected] (so that we can import the styles from node_modules, not a downloaded version)
- @fortawesome/[email protected] (so that we can import the styles from node_modules, not a downloaded version)
- [email protected] (so that we can import the styles from node_modules, not a downloaded version)
- [email protected] (and deleted the downloaded version of Bootstrap)
- [email protected] (so we can import bootstrap from node_modules)
@fullcalendar/core 5.3.0 → 5.5.1
@fullcalendar/daygrid 5.3.0 → 5.5.0
@fullcalendar/interaction 5.3.0 → 5.5.0
chart.js 2.9.3 → 2.9.4
list.js 1.5.0 → 2.3.1
moment 2.27.0 → 2.29.1
next 9.5.2 → 10.0.6
next-compose-plugins 2.2.0 → 2.2.1
next-transpile-modules 4.1.0 → 6.1.0
nouislider 14.6.1 → 14.6.3
react 16.13.1 → 17.0.1
react-chartjs-2 2.10.0 → 2.11.1
react-copy-to-clipboard 5.0.2 → 5.0.3
react-datetime 2.16.3 → 3.0.4
react-dom 16.13.1 → 17.0.1
react-notification-alert 0.0.12 → 0.0.13
react-to-print 2.9.0 → 2.12.2
reactstrap 8.5.1 → 8.9.0
webpack 4.44.1 → 4.46.0
The following warnings will appear when running the installation command, but they do not affect the UI or the functionality of the product (they will be solved in our next update):
npm WARN [email protected] requires a peer of react@^16.3.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react-dom@^16.3.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.3.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react-dom@^16.3.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.3.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react-dom@^16.3.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.5.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^0.14.9 || ^15.3.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^0.14.0 || ^15.0.0-rc || ^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react-dom@^0.14.0 || ^15.0.0-rc || ^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of [email protected] || ^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^0.14.0 || ^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
If they will persist in our 2.. version, we will drop their usages and replace them with other plugins. In development mode, some of the above plugins will throw a warning because they still use React v16 syntax. If the error will persist in our 2.. version, we will drop their usage and replace them with other plugins.
- Started project with NextJS
- Added design from Argon Dashboard PRO React by Creative Tim
Warnings might appear while doing an npm install - they do not affect the UI or the functionality of the product, and they appear because of NodeJS and not from the product itself. While in development some of the plugins that were used for this product will throw some warnings - note, this only happens in development, the UI or the functionality of the product is not affected, also, if the issues will persist in React 17, we'll drop usage of those plugins, and replace them with other ones.