Update dex, sqlite, mysql, mongodb, postgres deps for compatibility with the latest deno v1.16.2 #307
Conversation
dex: update to the version that uses std@0.115.1, instead
of the latest version of jspm-core, which could be dangerous
when jspm-core pushes the latest braking code.
aghussb/dex#3
sqlite: update to v3.1.3, it contains braking changes
so this PR fixes them too.
mysql: minor upgrade to v2.10.1 (from v2.10.0)
mongodb: update to v0.28.0, because the old version
is not compatible with the latest deno.
postgres: update to v0.14.2 and fix update postgres-connectors,
because the old version is not compatible with the
latest deno.
The changes are tested on deno v1.16.2.
Zhomart
changed the title
eveningkid
left a comment
eveningkid
left a comment
There was a problem hiding this comment.
First of all, thank you for your work Zhomart, it is highly appreciated!
For some reason, I missed the email and then got many notifications from linked issues. I am happy your work will help everybody else!
You'll find a few comments/questions below. If I can get your feedback on these, that would be helpful to move this forward.
Have a great day, talk soon :)
|
Thanks eveningkid for reviewing! |
eveningkid
left a comment
eveningkid
left a comment
There was a problem hiding this comment.
Thank you again for making all the changes :)
Please find below the last tiny tweak and we're good to merge!
|
Cool, I'll merge and create a new release! Have a great day Zhomart :) |
|
Thank you for your great work!!! For me this fixed my problem ;) It even works with deno version 1.16.4. Hopefully it won't break with tomorrow releasing version 1.17.0... |
4 participants
Update dex, sqlite, mysql, mongodb, postgres deps for compatibility with the latest deno v1.16.2
of the latest version of jspm-core, which could be dangerous
when jspm-core pushes the latest breaking code.
Use the latest deno node deps aghussb/dex#3
so this PR fixes them too.
is not compatible with the latest deno.
because the old version is not compatible with the latest deno.
The changes are tested on deno v1.16.2.
Fixes: #303, #302