Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue: Long File Paths Causing Build Failures on Windows #42

Open
imlegolas opened this issue Oct 9, 2024 · 0 comments
Open

Issue: Long File Paths Causing Build Failures on Windows #42

imlegolas opened this issue Oct 9, 2024 · 0 comments

Comments

@imlegolas
Copy link

Issue: Long File Paths Causing Build Failures on Windows

Description

When using the @mergeapi/merge-node-client package, the build process fails on Windows due to long file paths. This issue occurs during the AWS SAM build process.

Error Message

Building codeuri: C:\Users\Joshua\Documents\WorkRepos\test-integration runtime: nodejs20.x metadata: {} architecture: arm64 functions: GetUsersFunction, MergeDevIntegrationFunction
Running NodejsNpmBuilder:NpmPack
Running NodejsNpmBuilder:CopyNpmrcAndLockfile
Running NodejsNpmBuilder:CopySource
Running NodejsNpmBuilder:NpmInstall
Running NodejsNpmBuilder:CleanUpNpmrc
Running NodejsNpmBuilder:LockfileCleanUp

Error: [Errno 2] No such file or directory: 'C:\Users\Joshua\Documents\WorkRepos\test-integration\.aws-sam\build\MergeDevIntegrationFunction\node_modules\@mergeapi\merge-node-client\api\resources\accounting\resources\purchaseOrders\client\requests\PurchaseOrdersLineItemsRemoteFieldClassesListRequest.d.ts'

Resolution

I resolved the issue by enabling long paths in the Windows registry by setting the LongPathsEnabled key value to 1.

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

No branches or pull requests

1 participant