bump: tough-cookie version upgraded #3032
Closed
Conversation
This file contains 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.
Purpose
Punycode deprecation warning starting from Node 22
Approach
tough-cookie 4 has "secure" option in getCookieStringSync.
We use it to allow secure cookies access from localhost.
tough-cookie 5 does not have "secure" option.
It now gets it from protocol only which does not look whether it is localhost or not.
This is blocking us now to move from v4 to v5.
Perhaps v6 will include support for localhost.
References
There is an issue on this matter:
salesforce/tough-cookie#382
Pre-Merge TODO