v1.3.2

• Update dependencies
• Fix installation issue

v1.3.1

• Update the dependencies
• Migration to React 18
• Migration to sass from node-sass

1.3.0: Updated dependencies

[1.3.0] 2021-03-24

Bug fixing

• Changed the way we import images
  • Old way: require("path/to/imgae")
  • New way: require("path/to/imgae").default

Major style changes

Deleted components

Added components

Deleted dependencies

• react-bootstrap-switch (replaced by the simple Bootstrap Switch: https://reactstrap.github.io/components/form/#Custom-Inputs)

Added dependencies

• [email protected]
• [email protected] (Only to stop warnings from Bootstrap)

Updated dependencies

moment            2.26.0   →   2.29.1
node-sass         4.14.1   →    5.0.0
nouislider        14.5.0   →   14.6.4
react            16.13.1   →   17.0.2
react-datetime    2.16.3   →    3.0.4
react-dom        16.13.1   →   17.0.2
react-scripts      3.4.1   →    4.0.3
reactstrap         8.4.1   →    8.9.0
typescript         3.9.5   →    4.2.3

Warning

When doing a clean install, you might have some warnings, those come from node_modules and do not affect the project in any way.
The following two error might occur while doing a clean install - They do not affect the product in any way:
npm WARN [email protected] requires a peer of react@^16.5.0 but none is installed. You must install peer dependencies yourself.
npm WARN @babel/[email protected] requires a peer of @babel/core@^7.13.0 but none is installed. You must install peer dependencies yourself.

Updated dependencies

[1.2.0] 2020-06-12

Bug fixing

• #2 (changed the fonts import to ~assets/fonts and also added assets path inside jsconfig.json file)
• Other Paper React products issues solved here as well
  • creativetimofficial/ct-paper-kit-pro-react#2
  • creativetimofficial/paper-dashboard-react#15
  • creativetimofficial/paper-dashboard-react#8
  • creativetimofficial/ct-paper-dashboard-pro-react#8
  • creativetimofficial/ct-paper-dashboard-pro-react#6 - solution to this is to change the usage of the ModalHeader from reactstrap to simple Bootstrap ones:
    So, instead of:

<ModalHeader className="justify-content-center" toggle={this.toggleModalDemo}>
    Modal Title
</ModalHeader>

You should use

<div className="modal-header justify-content-center">
  <button type="button" className="close" data-dismiss="modal" aria-label="Close" onClick={this.toggleModalDemo}>
    <span aria-hidden="true">×</span>
  </button>
  <h5 className="modal-title">Modal Title</h5>
</div>

Major style changes

• src/assets/scss/paper-kit/_nucleo-outline.scss (changed the fonts import to ~assets/fonts and also added assets path inside jsconfig.json file)
• src/assets/scss/paper-kit/_nucleo-icons.scss (changed the fonts import to ~assets/fonts and also added assets path inside jsconfig.json file)
• src/assets/scss/react/plugins/_plugin-nouislider.scss (due to new noUiSlider API)

Deleted components

Added components

Deleted dependencies

Added dependencies

• [email protected] (for Creative Tim copyrights)
• [email protected] (for Creative Tim copyrights)

Updated dependencies

moment             2.24.0   →    2.26.0
node-sass          4.12.0   →    4.14.1
nouislider         13.1.5   →    14.5.0
react              16.8.6   →   16.13.1
react-dom          16.8.6   →   16.13.1
react-router        5.0.1   →     5.2.0
react-router-dom    5.0.1   →     5.2.0
react-scripts       3.0.1   →     3.4.1
reactstrap          8.0.0   →     8.4.1
typescript          3.5.2   →     3.9.5

Warning

All the following products: Paper Kit React, Paper Dashboard React, Paper Kit PRO React and Paper Dashboard PRO React have been updated together, and thus, we've added to all of them the same version of 1.2.0 - we may have skipped some versions for some of the above products, we've done so, since we want all Paper & React products to share the same versions.
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.
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.