Sami Jaber
Sami Jaber
@shyam-builder i assume we can close this PR?
@mimoid-prog We made a fix for the specific issue you shared a screenshot of. However, another issue persists. It is specifically tied to the Content Input `favoriteTechStack` being a localized...
@FutureFutureTo Are you still experiencing this issue? I am closing this issue due to staleness, but please feel free to reopen if the problem persists.
Yes, there is an issue with the types not propagating correctly for certain TS configurations. We will investigate this, thanks for reporting. The import itself should work correctly on the...
@jaydubb12 the `initializeNodeRuntime` function is only needed for certain production Node.js environments (such as Vercel) which tend to apply additional bundling steps that may remove sub-dependencies from the server bundle...
@jaydubb12 I am not following. What issue are you encountering exactly? Please provide a detailed breakdown with error logs and how you've integrated the SDK. If your issue is unrelated...
Closing this issue as the types declaration problem has been fixed already.
@jbool24 Thanks for filing as a separate issue. To answer your question: our Vue SDK is perfectly stable and reliable on Vue 3 (with or without Nuxt 3). It has...
You do not need to worry about why the api-key is needed, or when it is used. THe SDK takes care of that. We do have internal tickets tracking an...
@Joepocalyptic Can you try 1.0.28? It includes a fix for ESM types https://github.com/BuilderIO/builder/blob/main/packages/sdks/output/vue/CHANGELOG.md#1028