-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support runtimeConfig #32
Comments
I have added the support in my pr :) |
Where is this feature? We've come to realize that we cannot use Storyblok with our Nuxt site unless it supports runtimeConfig, or another method of utilizing a preview key in our non production environments, and a public key on our production environment without recompiling the source. |
Hi! Can you please explain/show how? :( |
There is a workaround. I'm using preview token for all envs, and just keep version draft/published in Per docs:
Setup Example:
|
@coremyslo Perfect workaround, thanks a lot! Still requires to add version manually on every request.. but that's the best we have now! |
As this issue was created when this module was used for Nuxt 2, we will focus on the support on the new issue -> #217 and close this one. For the same issue in the Nuxt 2 module, go to -> https://github.com/storyblok/storyblok-nuxt-2/issues |
Right now the
accessToken
is compiled into the plugin. Would be great if storyblok would support nuxt runtimeConfig.Example how @nuxtjs/axios implemented it: nuxt-community/axios-module@351ea5e
The text was updated successfully, but these errors were encountered: