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
TypeScript may cause issues because our SvelteKit app is already built when the build output lands in functions/lib/<site name>/.
How should this be recommended to users? If they include the compiled relative import in the uncompiled TS then the app may attempt to be recompiled by the TS compilation of the functions, which we do not want 🤔
This relative dir will be correct in the compiled code in functions/lib/index.js, but if the SvelteKit code is also passed through the TS compiler then we may have issues.
The text was updated successfully, but these errors were encountered:
Describe the bug
TypeScript may cause issues because our SvelteKit app is already built when the build output lands in
functions/lib/<site name>/
.How should this be recommended to users? If they include the compiled relative import in the uncompiled TS then the app may attempt to be recompiled by the TS compilation of the functions, which we do not want 🤔
EG:
This relative dir will be correct in the compiled code in
functions/lib/index.js
, but if the SvelteKit code is also passed through the TS compiler then we may have issues.The text was updated successfully, but these errors were encountered: