(Re-posting my answer to avoid puppy-socket.) Using the compilerOptions.baseUrl property I was able to do the below import. This allowed me to have a complete root-to-expected-path, which helps my code maintainance, and works in any file, independently of the current folder. The below examples will have the src folder of my project as the modules … Read more
I have fixed the issue. I added a new package: @angular/animations. import { BrowserAnimationsModule } from ‘@angular/platform-browser/animations’; And I imported the module: @NgModule({ imports: [ BrowserAnimationsModule ] })
The actual solution is given in a comment by @Paleo in @hirikarate’s answer: Imports should be declared inside the module declaration. Example: declare module ‘node-helper-lib’ { import * as SomeThirdParty from ‘node-helper-lib’; interface Helper { new(opt: SomeThirdParty.Options): SomeThirdParty.Type } export = Helper; }