fix: update microbundle [PER-152] #1
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Al migrar el crypto service a node 22 se ha roto la instalación de depencias. El problema está en la librería DIDComm-JS, concretamente en el bundler que la empaqueta, que depende de una librería ya deprecada que no compila por dependencias que las nuevas imágenes no cumplen, como el tener Python 2.7.
Esta PR actualiza el bundler a la última versión disponible y el problema se soluciona.
Sin embargo, esta PR se va a dejar en DRAFT y no se va a mergear, al menos de momento. El motivo es que la rama master está sincronizada con el repositorio original, que a su vez está archivado.
En un futuro habrá que decidir, por un lado, si se sigue manteniendo soporte con didcom v1, y si es así, si se sigue utilizando esta librería u otra, y si se mantiene esta, si tiene sentido renombrarla y romper con la original.
What type of PR is this? (check all applicable)
Related Tickets & Documents
https://izertis.atlassian.net/browse/PER-152
Screenshots/Recordings that might be useful
Added tests?
Added to documentation?
[optional] Are there any post-deployment tasks we need to perform?