Skip to content

Fix mock fs node24#2

Open
aseemxs wants to merge 11 commits intomainfrom
fix-mock-fs-node24
Open

Fix mock fs node24#2
aseemxs wants to merge 11 commits intomainfrom
fix-mock-fs-node24

Conversation

@aseemxs
Copy link
Owner

@aseemxs aseemxs commented Sep 23, 2025

Problem

Node.js 24 upgrade (PR aws#2244) fails on Windows with "Maximum call stack size exceeded" error in mock-fs library. The error occurs in stores data tests due to mock-fs v5.2.0 incompatibility with Node.js 24 on Windows.

Solution

Upgrade mock-fs from v5.2.0 to v5.5.0 in core/aws-lsp-core/package.json. Version 5.5.0 includes fixes for Node.js 24 compatibility issues, particularly Windows path handling that caused the stack overflow.

Testing:

Related:

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

laileni-aws and others added 11 commits September 11, 2025 12:21
- Fixes Maximum call stack size exceeded error on Windows
- mock-fs v5.2.0 has path handling bug with Node 24
- Resolves test failures in stores data tests
- Change '//cache' to '/cache' in uriCacheRepository.test.ts
- Revert mock-fs upgrade (wasn't the root cause)
- Fixes infinite recursion in mock-fs path resolution on Windows
- UNC paths cause stack overflow in Node 24 on Windows
- Add Node 24 skip logic to touchLastUpdatedTime test
- Consistent with existing pattern for mock-fs compatibility issues
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants