You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
The text was updated successfully, but these errors were encountered:
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
?--port
) and accessing the CLI from that port:4280
ℹ️ 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:Note that the same error occur is the website is in a subfolder, and the API
package.json
at the root of the repo (maybe a more common scenario), see https://github.com/sinedied/swa-functions-root-bug/tree/api-rootTo Reproduce
swa deploy
Expected 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.
The text was updated successfully, but these errors were encountered: