fix(utils): encode and decode base64 without Buffer

[sasjs-dev]

Closes #276.

encodeToBase64 and decodeFromBase64 used Buffer, which does not exist in a browser. utils/index.ts re-exports both from the package root, so every consumer importing @sasjs/utils carried the reference into its browser bundle. While those bundles shipped a Node polyfill tree the reference was silently shimmed; now that consumers are dropping that tree - the adapter's browser bundle no longer carries one - it is a ReferenceError waiting for the first caller.

Changes

• TextEncoder / TextDecoder carry the UTF-8 step. btoa is latin1, so encoding a password through it directly corrupts anything non-ASCII, and these values are stored.
• The binary string is built in chunks rather than spreading a whole byte array into String.fromCharCode, which overflows the call stack on long input.
• Whitespace is stripped before atob: Buffer ignores it when decoding and atob does not, so a wrapped or padded stored value still decodes.

The stored format is unchanged - the {sasjs_encoded} prefix, 200 hex characters of padding, and the fixed 200-character offset decodeFromBase64 strips - so credentials written by earlier releases keep decoding.

Tests

The failure mode is invisible in Node, so:

• a non-ASCII password round-trips, which is what a naive swap to btoa would break
• a round trip with the Buffer global deleted, which is the browser case
• the module code contains no Buffer reference, comments aside

Proven by reintroducing the Buffer implementation:

with Buffer:   ✕ should round-trip without a Buffer global
               ✕ should reference no Buffer in the module code
               ReferenceError: Buffer is not defined
               Tests: 2 failed, 6 passed, 8 total
with platform: Tests: 8 passed, 8 total

Full suite: 40 suites, 448 tests passing. tsc and prettier clean.

Why now

This is the last unguarded host global in a browser-facing module of this package - the same class as the process.platform reads fixed in #281. With both gone, a browser consumer of @sasjs/utils needs no polyfill for anything this package does itself.

[sasjs-dev]

Reviewed the full diff at e8e93df (base64 encode/decode moved off Buffer to TextEncoder/btoa/atob). The UTF-8 step is preserved on both sides, so the output stays byte-identical to the old Buffer path and previously stored values still decode; the chunked String.fromCharCode avoids the call-stack overflow on long input.

No blocking issues.

[sasjs-gha]

🎉 This PR is included in version 3.7.4 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀