[WINDOWS]Unable to upload artifactsshpk-conv)

[therepo90]

Description

sam package command not working

Steps to reproduce

sam init npm install request sam package --s3-bucket mybucket --output-template-file packaged.yaml

Observed result

Unable to upload artifact mystuff referenced by CodeUri parameter of mystuff resource. [WinError 123] 'C:\projects\myproj\.aws-sam\build\mystuff\node_modules\.bin\sshpk-conv'

Additional environment details (Ex: Windows, Mac, Amazon Linux etc)

1. OS: windows 10
2. Dependency: "request": "^2.88.0"

[bitconym]

Have the same issue with the .bin folder, and couldn't package the code on Windows 10.

[sriram-mv]

if request is a dependency, can you specify it in package.json and run sam build, and then try to package it?

[rebolyte]

I'm having the same issue on Win10. I run sam build --use-container, and then sam package fails: Unable to upload artifact MyFunction referenced by CodeUri parameter of MyFunction resource. [WinError 123] The filename, directory name, or volume label syntax is incorrect: 'C:\\projdir\\.aws-sam\\build\\MyFunction\\node_modules\\.bin\\detect-libc'. If I don't specify --use-container it uploads just fine. I have all modules used in my package.json.

Using aws cloudformation package --debug doesn't seem to provide anything more useful than the exception.

There is some info around the error at neovim/neovim#6329 and these old MS docs say that it refers to The system does not accept the keyboard combination Alt+0 through Alt+32 or the following characters: \\ \\ / [ ] : | < > + ; = . ? ".

@TheSriram Anything to try here? I'm hoping the SAM CLI can help me avoid spinning up VMs just to do my Lambda builds.

[jfuss]

Given the age and no recent activity, I am assuming this has been fixed or is no longer an issue.

If that is not true, please open a new issue and we will have a deeper look into this.

[github-actions[bot]]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.