The Fix
If the problem is related to a NPM package the first thing to do is to update it to its latest version, as the author had most likely already experienced that and possibly came out with an update to properly address the new behaviour. If the issue is happening inside our own code, the best thing we can do is to fix that manually by adding the definite assignment assertion modifier like explained above: in most scenarios, a bunch of ! placed in the right spots will be enough fix your project.
If you cannot do that, we can choose to disable the new feature by setting the strictPropertyInitialization initialization flag to false in the compilerOptions section within our tsconfig.json configuration file; alternatively, we can also add the —strictPropertyInitialization false command-line switch to turn off this checking.
In the unlikely case both of the above fixes won’t be enough, try to temporarily downgrade to TypeScript <= 2.6 and see if the error persists.