Closed chaymafourati closed 5 years ago
@chaymafourati, were you able to confirm that the project still functions normally with upgraded dependencies? (Sometimes the APIs or dependencies of a library will change, causing a newer version to break despite an older version functioning properly.)
Related, it's best-practice to version-pin in a package.json
or requirements.txt
, even if you're upgrading to the newest version of a library, to guard against the above; using *
as a package.json
version can be dangerous.
updated the dependencies to latest version ( issue #599 )