feat(DEP0064): handle tls.createSecurePair deprecation#266
Conversation
|
Missing import test case
|
…d ESM default and dynamic import cases
…uded default and dynamic ESM imports + needed refactors as PR comments) WHAT Changed: - AST-based migration - ESM/default/dynamic cases - Normalize rewritten CJS requires to `node:tls` as suggested to code section - Remove duplicated `getNodeImportStatements/getNodeRequireCalls` invocations that attempted to handle `'node:tls'` vs `'tls'`
…d dynamic import (await/then) WHAT : - ESM default import - ESM dynamic import (await assignment) - ESM dynamic import (then callback)
…cation`)' into feat(`tls-createSecurePair-deprecation`)
|
Thanks for this! |
|
bump @technologic-technologic 👋 |
62a736a to
da7d3c8
Compare
|
@JakobJingleheimer i had take hand here, it's much more lighter |
2268a5e to
c7b610f
Compare
tls.createSecurePair deprecation
JakobJingleheimer
left a comment
There was a problem hiding this comment.
Thanks for this! The code is really readable / easy to follow 🙂
Sorry this took a while for me to get back to this. I was bereaved right after my last review and then lost track.
@brunocroh I think a lot of this is already handled by your fancy utils. Could you take a look?
|
@AugustinMauroy do you know what the problem with the CI is here? |
I'm going to check but I think something like that should fix it: this issue is dude to the fact that ast-grep (used for test on utility package) need to resolve by arch since it's node native add-on |
This pull request implements the codemod to replace deprecated
tls.createSecurePair()withTLSSocket, addressing DEP0064.tls.createSecurePair()depreciation #127Changes included:
createSecurePair(...)intonew TLSSocket(underlyingSocket, {...}), preservingtls.TLSSocketfor namespace usage.{ createSecurePair }with{ TLSSocket }in CJS/ESM (keeps namespace imports intact).pair→socketwhere applicable.This PR is part of the feature branch
feat/tls-createSecurePair-to-TLSSocket.