Currently on Angular version 4.3.2
Running @angular/cli version 1.2.6
Incorporating TypeScript (v2.4.2) for a specific component that imports
import {animate, AnimationEvent, state, style, transition, trigger} from '@angular/animations';
Encountering warnings similar to
"export 'AnimationEvent' was not found in '@angular/animations'
Interestingly, the other functions like animate, state, style, etc. do not trigger any warnings. Upon inspection of the @angular code within node_modules/@angular/animations.d.ts reveals
export * from './public_api';
Further exploration into ./public_api.d.ts exposes
export * from './src/animations';
and ./src/animations.d.ts contains
export { AnimationBuilder, AnimationFactory } from './animation_builder';
export { AnimationEvent } from './animation_event';
export { AUTO_STYLE, AnimateChildOptions, AnimateTimings, AnimationAnimateChildMetadata, AnimationAnimateMetadata, AnimationAnimateRefMetadata, AnimationGroupMetadata, AnimationKeyframesSequenceMetadata, AnimationMetadata, AnimationMetadataType, AnimationOptions, AnimationQueryMetadata, AnimationQueryOptions, AnimationReferenceMetadata, AnimationSequenceMetadata, AnimationStaggerMetadata, AnimationStateMetadata, AnimationStyleMetadata, AnimationTransitionMetadata, AnimationTriggerMetadata, animate, animateChild, animation, group, keyframes, query, sequence, stagger, state, style, transition, trigger, useAnimation, ɵStyleData } from './animation_metadata';
export { AnimationPlayer, NoopAnimationPlayer } from './players/animation_player';
export * from './private_export';
Additionally, ./animation_event.d.ts defines the interface
export interface AnimationEvent {
fromState: string;
toState: string;
totalTime: number;
phaseName: string;
element: any;
triggerName: string;
}
Interestingly enough, when copying the interface definition directly into my code, the functionality works seamlessly.
This scenario closely resembles numerous other import scenarios I've encountered, however, this is the sole occurrence resulting in warnings.
What steps can be taken to eliminate these warnings without resorting to manually adding the interface definition to my code?