uuidv4 return nan-undefinedundefined in browser #193
See original GitHub issueSteps:
- Install Angular 8
- Install uuid ^8.2.0
- Run project in development mode. Result is good (like 75442486-0878-440c-9db1-a7006c25a39f).
- Run project in production mode. Result is:
nan-undefinedundefined-undefinedundefined-undefinedundefined-undefinedundefinedundefinedundefinedundefinedundefined
OS: Windows 7 or 10 Browser: Chrome
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Date returning as "Undefined" and "NaN" in some browsers?
I have been trying to troubleshoot this all morning, and I cannot see anything that would be causing the return of "undefined NaN,...
Read more >uuidv4 - npm
Please note that the isUuid function returns true for both, v4 and v5 UUIDs. In addition, isUuid returns true for empty() . Using...
Read more >npm fails to install - Google Groups
7 verbose cache add name=undefined spec="appium" args=["appium",null] ... Returns NaN if string can\'t be parsed to number.\n\n```javascript\n_(\'2.556\').
Read more >pytest Documentation - Read the Docs
to assert that your function returns a certain value. ... A pytest plugin for console based browser test selection just after the collection ......
Read more >Speaking-JavaScript.pdf - Pepa
All major browsers have consoles for entering JavaScript that is evaluated in the ... (Reading an unknown property always returns undefined.) Objects.
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 FreeTop 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
Top GitHub Comments
@broofa
Yeah. I reproduced the bug in Angular 8. I have updated Angular to v9 and the bug does not reproduce any more.
Thank you.
@anton-marchenko thank you for taking the time to pull together the reproduction.
I was able to reproduce the issue with Angular 8.
The key thing that fixed it for me was upgrading
@angular-devkit/build-angular@0.801.3
to@angular-devkit/build-angular@0.901.12
@RezaRahmati can you give that a try?