-
-
Notifications
You must be signed in to change notification settings - Fork 37.1k
atob and btoa should not be marked as legacy #57145
Copy link
Copy link
Closed
Labels
docIssues and PRs related to Node.js documentation.Issues and PRs related to Node.js documentation.web-standardsIssues and PRs related to web-platform APIs and standards compliance.Issues and PRs related to web-platform APIs and standards compliance.
Description
Activity
Metadata
Metadata
Assignees
Labels
docIssues and PRs related to Node.js documentation.Issues and PRs related to Node.js documentation.web-standardsIssues and PRs related to web-platform APIs and standards compliance.Issues and PRs related to web-platform APIs and standards compliance.
Affected URL(s)
https://nodejs.org/docs/latest/api/globals.html#atobdata https://nodejs.org/docs/latest/api/buffer.html#bufferatobdata
Description of the problem
hey!
i notice that
atobandbtoaare marked as Legacy, which states "no longer actively maintained, and other alternatives are available".some notes on that:
JSON.parse(atob(b64)))having these marked as legacy also seems to go against the very good direction node has taken recently of compatibility with web apis like the webstreams api
i think it would be great if these were marked Stability 2! what do you think?