Optimizing problem
See original GitHub issueIssue Description
Hi,
i have a problem with your great timepicker library when i made a ng build --prod
with optimizing (which is default in prod).
Then I get this error:
iN.getHours is not a function
I find out that the uglified iN
stands for the TimepickerTime namespace. But it is empty after the build.
It works with angular build option optimizing=false and in dev environment.
Very strange behaviour o.O and I do not have an idea of a solution after 6 hours!
Tested with Angular (Core/Material/CLI) version 6.0.0 and 7.1.4.
Yours sincerely, Philipp
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (7 by maintainers)
Top Results From Across the Web
5.8 Optimization Problems
Guideline for Solving Optimization Problems. · Identify what is to be maximized or minimized and what the constraints are. · Draw a diagram...
Read more >Optimization - Calculus I - Pauls Online Math Notes
In optimization problems we are looking for the largest value or the smallest value that a function can take. We saw how to...
Read more >Optimization Problems - Calculus - YouTube
This calculus video explains how to solve optimization problems. It explains how to solve the fence along the river problem, ...
Read more >How to Solve ANY Optimization Problem [Calc 1] - YouTube
Optimization problems are like men. They're all the same amirite?
Read more >Optimization Problem #1 - YouTube
You da real mvps! $1 per month helps!! :) https://www.patreon.com/patrickjmt !! Optimization Problem #2 ht...
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
Seems like it’s working now, thank you.
Could you please update to v3.0.3 and check?