storyblok-nuxt | Storyblok Nuxt.js module | Content Management System library
kandi X-RAY | storyblok-nuxt Summary
kandi X-RAY | storyblok-nuxt Summary
Storyblok Nuxt.js module
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of storyblok-nuxt
storyblok-nuxt Key Features
storyblok-nuxt Examples and Code Snippets
Community Discussions
Trending Discussions on storyblok-nuxt
QUESTION
I'm using storyblok-nuxt module. I plugged it in nuxt.cofig.js
and it works fine in page when I call it directly in the asyncData method as such:
ANSWER
Answered 2020-May-17 at 15:46Using storyapi
with Nuxt is very easy. In your asyncData you can dispatch your action like:
QUESTION
Solved! Look bellow for more details. (It was a typo mistake)
I am trying to Deploy a project in Netlify as Static using npm run generate
but I am getting an error of failed during stage 'building site': Build script returned non-zero exit code: 1
. I have previously deployed 2 other projects in Netlify (they weren't using Storyblok, only Nuxt) and I haven't had such an error before.
The project uses Nuxt Js (Vue Js framework), Vuetify and Storyblok Headless CMS with asyncData
methods calling the requests. I have implemented it the way Storyblok's documentation says, especially the generation of the routes in nuxt.config.js
, the dynamically change of the version
(draft - published), using the storyblok-nuxt
module for the requests, setting up Storyblok space and creating the tokens (draft - published), the desired components and content.
Everything works fine, both locally as npm run dev
(development mode) and using npm run generate
(local production mode). I tested the second using the http-server
, it worked completely normally.
I tried :
1). Re-deploying without cache even.
2). Running locally npm run audit
and then npm run audit fix
to fix some vulnerabilities (to check if they were the problem by any chance).
3). Updated Nuxt to the newest version (it was 2.4.0 i think and I updated to 2.8.1.
4). I also tried commenting out the generation of the dynamic routes in the nuxt.config.js (so only the standard routes would be generated) to see if the dynamic routes are the problem but still similar error again.
The complete log in the Netlify Deployment is :
...ANSWER
Answered 2019-Jun-12 at 12:24I found the solution, it didn't have anything to do with either Nuxt specifically, Storyblok or anything else, it was basically a typo mistake.
I started cleaning up a bit the project from potential console.log(...)
that I had in various places, the idea was to see if this way the Netlify log would give me more details since they wouldn't be hidden from the console.logs.
After the clean up and the git push the next deploy had indeed a more clear error output in the console which helped me track the spot with the mistake. It was in a SectionImage
SVG Component that was basically with Nuxt's module for SVGs, I had written the name
attribute as Sectionimage
. So after fixing it everything worked perfectly!
(Nuxt - Vue - Vuetify and Storyblok (first time used it) rock! :D )
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install storyblok-nuxt
This module adds two objects to the the Nuxt.js context.
$storyapi: The Storyblok API client.
$storybridge: A loader for the Storyblok JS bridge that is responsible for adding the editing interface to your website.
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page