Skip to content

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

@imlegolas

Description

@imlegolas

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions