Before filing this issue, please ensure you're using the latest CLI by running swa --version and comparing to the latest version on npm.
Are you accessing the CLI from the default port :4280 ?
[ ] No, I am using a different port number (--port) and accessing the CLI from that port
[x] Yes, I am accessing the CLI from port :4280
Make sure you are accessing the URL printed in the console when running swa start!
ℹ️ NOTE: Make sure to enable debug logs when running any swa commands using --verbose=silly
Describe the bug
If I have a project with a static website at the root of the repo, and a function contained in an /api subfolder, I cannot deploy the function and get this error:
Desktop (please complete the following information):
OS: MacOS
Version 14.4
Additional context
It seems that the problem is due to the StaticSiteClient creating zip file of the artifacts in the current folder. Using a different temp folder might solve the issue.
Before filing this issue, please ensure you're using the latest CLI by running
swa --versionand comparing to the latest version on npm.Are you accessing the CLI from the default port
:4280?--port) and accessing the CLI from that port:4280ℹ️ NOTE: Make sure to enable debug logs when running any
swacommands using--verbose=sillyDescribe the bug If I have a project with a static website at the root of the repo, and a function contained in an
/apisubfolder, I cannot deploy the function and get this error:Note that the same error occur is the website is in a subfolder, and the API
package.jsonat the root of the repo (maybe a more common scenario), see https://github.com/sinedied/swa-functions-root-bug/tree/api-rootTo Reproduce
swa deployExpected behavior No errors.
Desktop (please complete the following information):
Additional context It seems that the problem is due to the StaticSiteClient creating zip file of the artifacts in the current folder. Using a different temp folder might solve the issue.