Skip to content

Updated dependencies

Latest
Compare
Choose a tag to compare
@einazare einazare released this 01 Feb 13:42
· 2 commits to master since this release
7aa8a4a

[1.1.0] 2021-02-01

Bug fixing

Major style changes

Deleted components

Added components

Deleted dependencies

  • @types/googlemaps
  • @types/markerclustererplus
  • react-google-maps (we'll use simple Google Maps API with Vanilla JS instead)
  • webpack (next will install the appropriate one)

Added dependencies

Updated dependencies

@material-ui/core       4.11.0   →   4.11.3
@material-ui/icons       4.9.1   →   4.11.2
next                     9.5.2   →   10.0.5
next-compose-plugins     2.2.0   →    2.2.1
next-images              1.3.1   →    1.7.0
react                  16.13.1   →   17.0.1
react-dom              16.13.1   →   17.0.1
typescript               3.9.7   →    4.1.3

Warning

Warning

At the moment, the pages/_app.js and pages/_document.js could not be converted to functional components - for HOOK support, since they still need some of the class comments life-cycle methods. Please check this here: https://nextjs.org/docs/advanced-features/custom-document.
The TypeScript dependencies are installed only to stop console warnings on install. They are not actually used in our product. So the product is not based on TypeScript!
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@^0.14.9 || ^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@^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@^16.3.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.