Getting `TypeError: Stringified UUID is invalid` error
See original GitHub issueDescribe the bug
I used uuid in Angular project and calling v4, when serving angular with ng serve
option it works fine, when building angular for prod by ng build --prod
or serving in prod mode by ng serve --prod
, it throws TypeError: Stringified UUID is invalid
exception
To Reproduce
Steps to reproduce the behavior:
1- create angular project 2- npm install uuid 3- call uuid v4 in component or service
Expected behavior
Generate a guid
Runtime
- OS: Windows, MacOs
- Runtime: Node 10,
- Runtime Version: v8
Additional context
work around
Downgrading to v7.0.3 solved the issue
Issue Analytics
- State:
- Created 3 years ago
- Reactions:8
- Comments:14 (8 by maintainers)
Top Results From Across the Web
JSON.Stringify error "Cannot Read Property [uuid] of ...
The problem I'm running into is that now, when I attempt to save files, I'm getting this error at JSON.stringify() :
Read more >uuid - npm
uuid.stringify(), Convert array of bytes to UUID string, New in uuid@8.3 ... throws, Error if more than 10M UUIDs/sec are requested ...
Read more >Package Diff: uuid @ 8.2.0 .. 8.3.0-beta.0
+ throw TypeError('Stringified UUID is invalid'); ... + get: function () { ... Uint8Array(16);function t(){if(!n)throw new Error("crypto.
Read more >Node.js NPM uuid - GeeksforGeeks
uuid.stringify(), Convert array of bytes to UUID string ... Get route to display HTML form ... throw new Error(.
Read more >DA: Getting license error like: Invalid UUID string - Micro Focus
DA: Getting license error like: Invalid UUID string. After copying a DA database to a new DA server, get errors with licensing. No...
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
With @angular-devkit under @angular7 caused the same issue on the production. But downgrading to uuid@v7.0.3 worked out.
Unfortunately I do not have the time right now to provide an example for this but I confirm that @angular-devkit/build-angular@~0.803.15 works, anything less than that doesn’t. @ctavan thanks dude you saved me lots of headache.