assert missing crypto.randomUUID #8301
Conversation
runspired
added
🎯 canary
linking usually works better with pnpm than with yarn or npm but as long as you link with whatever you are using to install in the app it should be doable. I tend to just test in the test apps though to avoid these sorts of troubles. |
| @@ -41,6 +41,10 @@ if (macroCondition(getOwnConfig<{ polyfillUUID: boolean }>().polyfillUUID)) { | |||
| } | |||
|
|
|||
| function uuidv4(): string { | |||
| assert( | |||
There was a problem hiding this comment.
note asserts only trigger in dev build, so if deploying to an insecure environment as mentioned in https://discord.com/channels/480462759797063690/486549196837486592/1040645066504556564 the error will still be simply that randomUUID is not a function.
There was a problem hiding this comment.
(also note, even for internal tools, if you aren't deploying production builds with https you very much should be for a host of reasons)
Description
Add a little assert message when crypto.randomUUID does not exist
Sidenote: I was not able to test this, since I wasnt able to boot an app with the linked ember-data. :(