Usa o módulo crypto
para gerar UUIDs e move o uuid
para devDependencies
#1725
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Mudanças realizadas
Esbarrei com o PR #1018 e decidi reimplementar. Não foi possível remover a biblioteca
uuid
, porque usamos uma função dela para verificar a versão do UUID em testes, mas foi possível passar a bibliotecauuid
para ser uma dependência de desenvolvimento e utilizar o módulocrypto
para gerar os UUIDs com.randomUUID()
.O módulo deve ser importado como
crypto
ao invés denode:crypto
nos arquivos que são executados em Middlewares Edge da Vercel, conforme documentação (aqui e aqui).Tipo de mudança
Checklist: