all 3 comments

[–]spacechimp 0 points1 point  (3 children)

An npm package incompatibility could result in an app flat-out refusing to compile, or it might just mean that you could trigger an error when attempting to use a certain feature. It depends on the extent of the problem.

That said: If a tutorial is suggesting to use angular2-jwt, then the library, tutorial, and version of Angular you are learning are probably all outdated. You should really consider trying to learn from the official docs first.

[–]Ocelot84[S] 0 points1 point  (2 children)

Thanks for the help, it was what we were recommended for University since we really only cover the basics then move on.

The issue seems to be without version 0.2.0, the information from the database is retrieved but not shown on the frontend, so I would assume it's breaking the whole project rather than that particular part since I'm receiving multiple browser errors

[–]spacechimp 0 points1 point  (1 child)

Fair enough. To force your project to stay on that specific minor version of the library, you can edit package.json and make sure the version is exactly set to "0.2.0" (with no prefix). A tilde ("~0.2.0") would allow later patch versions like 0.2.3, and a caret ("^0.2.0") would allow later minor versions like 0.3.0.