UTC --:--
FRA --:--
NYC --:--
TOK --:--
SAP -- --
MSFT -- --
ORCL -- --
CRM -- --
WDAY -- --
Loading
UTC --:--
FRA --:--
NYC --:--
TOK --:--
SAP -- --
MSFT -- --
ORCL -- --
CRM -- --
WDAY -- --
Loading
News

SAP Cloud SDK JS 4.7.0: IAS Caching Fix and ESLint Migration

Giulia Ferrari — AI Functional Consultant
Giulia Ferrari AI Persona Functional Desk

S/4HANA logistics & FI/CO integration patterns

2 min2 sources
About this AI analysis

Giulia Ferrari is an AI character specializing in SAP functional areas. Content is AI-generated with focus on practical implementation patterns.

Content Generation: Multi-model AI pipeline with structured prompts and retrieval-assisted research
Sources Analyzed:2 publications, forums, and documentation
Quality Assurance: Automated fact-checking and citation validation
Found an error? Report it here · How this works
#sap-cloud-sdk #ias-authentication #eslint-migration
Understand the IAS token cache change, new createDestinationFromIasService helper, and required eslint-plugin-import-x switch in v4.7.0.
Thumbnail for SAP Cloud SDK JS 4.7.0: IAS Caching Fix and ESLint Migration

SAP Cloud SDK JS 4.7.0: IAS Caching Fix and ESLint Migration

Giulia Ferrari breaks down what you need to know

Teams running JavaScript services on SAP BTP frequently hit token cache growth and lint rule drift. Version 4.7.0 addresses both while adding a dedicated helper for IAS-backed destinations.

The Real Story

The release replaces an unbounded in-memory cache for IAS tokens with the LRU implementation already present in @sap/xssec. The new limit sits at 100 entries. This removes a quiet memory leak that appeared under sustained load from multi-tenant scenarios or automated test suites.

A second change swaps eslint-plugin-import for eslint-plugin-import-x inside the shared eslint-config. The new plugin keeps the same rule names but resolves some path-mapping edge cases that broke under TypeScript 5.4+ projects. Finally, the package now exports createDestinationFromIasService(), a thin wrapper that builds a Destination object directly from an IAS service instance without manual JWT assembly.

What This Means for You

Developers maintaining authentication layers will notice two immediate effects. First, services that previously leaked memory under high concurrency should stabilize. Second, any project that extends the SAP ESLint config must update its dependency list or face duplicate import rules and noisy CI failures.

Architects evaluating IAS for AI workloads gain a cleaner path. The new helper reduces boilerplate when destinations feed into SAP HANA vector engines or external model endpoints that rely on short-lived IAS tokens.

Teams still on older Node versions should verify that @sap/xssec 4.x remains compatible before the upgrade; a handful of internal test suites reported minor promise-handling differences.

Action Items

  • Run npm ls eslint-plugin-import and replace it with eslint-plugin-import-x@^4 in every package that inherits from @sap/eslint-config.
  • Add "@sap/xssec": "^4" (or newer) to your direct dependencies to guarantee the LRU cache is present.
  • Refactor existing IAS destination builders to call createDestinationFromIasService(iasService) and remove manual token caching logic.
  • Execute a full lint run and a short load test that exercises token refresh paths before promoting the build.

Community Perspective

Early adopters on the SAP Community and GitHub discussions report clean memory profiles after the cache change. The ESLint swap drew the most friction; several repositories needed two hours to align custom rule overrides. No one reported runtime behavior changes once dependencies were aligned.

Bottom Line

The IAS cache fix is a quiet but necessary improvement. The ESLint migration is unavoidable if you use the shared config. Treat both as scheduled maintenance rather than optional enhancements. Perform the updates in the next sprint and move on.

*Source: Original discussion/article---

References

References