Skip to content

test(build): resolve fsSafe.js to its real source in the packaging check - #162

Merged
kaanozhan merged 1 commit into
mainfrom
fix/build-files-test-fssafe
Sep 26, 2026
Merged

kaanozhan merged 1 commit into
mainfrom
fix/build-files-test-fssafe

Conversation

@kaanozhan

Copy link
Copy Markdown
Owner

Problem

After merging #160 and #161, test/buildFiles.test.js fails on main:

add these to package.json build.files: scripts/fsSafe.js

STR-01 (#161) ships the app's own src/main/fsSafe.js into .frame/bin/, but the packaging check from #160 assumed every copied file comes from scripts/. Each PR was green on its own; the failure only appears once both are merged.

Fix

The check maps fsSafe.js to its real source, src/main/fsSafe.js, which src/**/* already packages. No packaging change is needed.

Verification

npm test: 978/978 passing.

STR-01 ships the app's own src/main/fsSafe.js into .frame/bin/, while the
build.files check from #160 assumed every copied file comes from scripts/.
Both PRs were green on their own; together the check reported a missing
scripts/fsSafe.js. The file is packaged through src/**/*, so only the
check's source mapping was wrong.
@kaanozhan
kaanozhan merged commit 3f0eaf7 into main Sep 26, 2026
2 checks passed
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.

1 participant