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
{{ message }}
This repository has been archived by the owner on Jan 11, 2023. It is now read-only.
Sapper is assuming the current working directory is similar to development, however in some situations the cwd may be different. For example in my deployment to google cloud functions, I have a deeper directory structure, placing my sapper app in a deep folder from the path where the function is run.
Something like a SAPPER_APP_DIR, SAPPER_BASE_DIR or something similar should be configured to allow for running the app without relying on cwd.
I experimented with using SAPPER_DEST, and assuming that app would be one level above this, however that is not the case for export and breaks that test.
The text was updated successfully, but these errors were encountered:
For example here:
https://github.com/sveltejs/sapper/blob/master/src/middleware/index.ts#L117
Sapper is assuming the current working directory is similar to development, however in some situations the cwd may be different. For example in my deployment to google cloud functions, I have a deeper directory structure, placing my sapper app in a deep folder from the path where the function is run.
Something like a SAPPER_APP_DIR, SAPPER_BASE_DIR or something similar should be configured to allow for running the app without relying on cwd.
I experimented with using SAPPER_DEST, and assuming that
app
would be one level above this, however that is not the case forexport
and breaks that test.The text was updated successfully, but these errors were encountered: