Drawer Component Broken
See original GitHub issueng -v:
_ _ ____ _ ___
/ \ _ __ __ _ _ _| | __ _ _ __ / ___| | |_ _|
/ △ \ | '_ \ / _` | | | | |/ _` | '__| | | | | | |
/ ___ \| | | | (_| | |_| | | (_| | | | |___| |___ | |
/_/ \_\_| |_|\__, |\__,_|_|\__,_|_| \____|_____|___|
|___/
@angular/cli: 1.2.0-beta.0
node: 6.10.3
os: darwin x64
@angular/animations: 4.2.2
@angular/common: 4.2.2
@angular/compiler: 4.2.2
@angular/core: 4.2.2
@angular/flex-layout: 2.0.0-beta.8
@angular/forms: 4.2.2
@angular/http: 4.2.2
@angular/material: 2.0.0-beta.6
@angular/platform-browser: 4.2.2
@angular/platform-browser-dynamic: 4.2.2
@angular/router: 4.2.2
@angular/cli: 1.2.0-beta.0
@angular/language-service: 4.2.2
Same code as the example here: https://swimlane.github.io/ngx-ui/#drawer
Stack:
RROR Error: Unable to resolve animation metadata node #undefined
at visitAnimationNode (browser.es5.js:833)
at AnimationAstBuilderVisitor.webpackJsonp.../../../animations/@angular/animations/browser.es5.js.AnimationAstBuilderVisitor.build (browser.es5.js:952)
at buildAnimationAst (browser.es5.js:934)
at InjectableAnimationEngine.webpackJsonp.../../../animations/@angular/animations/browser.es5.js.AnimationEngine.registerTrigger (browser.es5.js:4495)
at animations.es5.js:243
at Array.forEach (<anonymous>)
at AnimationRendererFactory.webpackJsonp.../../../platform-browser/@angular/platform-browser/animations.es5.js.AnimationRendererFactory.createRenderer (animations.es5.js:243)
at DebugRendererFactory2.webpackJsonp.../../../core/@angular/core.es5.js.DebugRendererFactory2.createRenderer (core.es5.js:13567)
at createComponentView (core.es5.js:12171)
at callWithDebugContext (core.es5.js:13535)
View_DrawerComponent_Host_0 @ DrawerComponent_Host.html:1
proxyClass @ compiler.es5.js:14962
webpackJsonp.../../../core/@angular/core.es5.js.DebugContext_.logError @ core.es5.js:13475
webpackJsonp.../../../core/@angular/core.es5.js.ErrorHandler.handleError @ core.es5.js:1080
(anonymous) @ core.es5.js:9303
(anonymous) @ platform-browser.es5.js:2668
webpackJsonp.../../../../zone.js/dist/zone.js.ZoneDelegate.invokeTask @ zone.js:424
onInvokeTask @ core.es5.js:3924
webpackJsonp.../../../../zone.js/dist/zone.js.ZoneDelegate.invokeTask @ zone.js:423
webpackJsonp.../../../../zone.js/dist/zone.js.Zone.runTask @ zone.js:191
ZoneTask.invoke @ zone.js:486
DrawerComponent_Host.html:1 ERROR CONTEXT DebugContext_ {view: Object, nodeIndex: 0, nodeDef: Object, elDef: Object, elView: Object}
Problem: Once I click to open the drawer I get the following stacktrace
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
How to Fix a Broken Drawer - The Home Depot
A drawer side slider component. Take a broken drawer out and inspect the gliders or sliders. Sliders can wear out from use and...
Read more >Material Ui Drawer Broken on Build - reactjs - Stack Overflow
Just change the variant of the Drawer component to "persistent": <Drawer variant='permanent' ... to <Drawer variant='persistent' .
Read more >drawer repair kit - Amazon.com
6 Set Drawer Repair Kit Drawer Support Brackets Includes Screws for Reinforcing and Repairing Broken Sagging Wood Drawers Furniture Hardware Accessories.
Read more >How To Fix A Broken Drawer Slide
To fix a broken drawer slide try adjusting the drawer slides to see if that will solve the problem. If not you can...
Read more >How to Replace Old Drawer Boxes - Cabinet Doors 'N' More
Guide to Replacing Broken Drawer Boxes ... If shipping with other components like Cabinet Doors, Drawer Fronts or accessories, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Good to hear that it got fixed in Angular. Sorry guys this bug showed up.
Fixed in latest
If your project is on 4.2 and your dependency that used animations was on 4.1 this error would occur.