jamstack

问题 in the latest version of Nuxt (2.14) they introduced an optimization for building the app when no code is changed (for drastically improve build times). I make websites in jamstack, deploy on netlify with nuxt generate and, until now, with target: 'server' . I tried the new target: 'static' in order to take advantage of this new feature, but my code won't build as it seems that in this mode the app can't access to this.$route in order to generate dynamic pages. So, my question is: how is this

问题 I have trouble with deploying the Next.js project to Netlify. It was working well yesterday but now I am getting errors while deployment. Here I attached error log screenshot and full log. 11:40:08 AM: Build ready to start 11:40:10 AM: build-image version: d84c79427e8f83c1ba17bcdd7b3fe38059376b68 11:40:10 AM: build-image tag: v3.6.1 11:40:10 AM: buildbot version: 734b021f1afb208e332629f2580fef69fda9a3bc 11:40:10 AM: Fetching cached dependencies 11:40:10 AM: Starting to download cache of 174

问题 I am not experienced in ES (my background is more of relational databases) and I am trying to achieve the goal of having a search bar in my web application to search the entire content of it (or the content I will be willing to index in ES). The architecture implemented is Jamstack with a gatsby application fetching content (sometimes at build time, sometimes at runtime) from a strapi application (headless cms). In the middle, I developed a microservice to write the documents created in the

问题 I am new to JAM stack. The web applications in JAM stack (I am hosting my app in Netlify ) will be completely relied upon APIs for storing info and authentication, right? So my concern is that I would have to expose all of my API keys publically in my JavaScript code. Anyone who knows how to open up the site source could see my API secrets and can be easily misused. I was reading through an open issue in JAM stack repo here on Github How can I secure my API Keys from eavesdropping and misuse?

问题 I am new to JAM stack. The web applications in JAM stack (I am hosting my app in Netlify ) will be completely relied upon APIs for storing info and authentication, right? So my concern is that I would have to expose all of my API keys publically in my JavaScript code. Anyone who knows how to open up the site source could see my API secrets and can be easily misused. I was reading through an open issue in JAM stack repo here on Github How can I secure my API Keys from eavesdropping and misuse?

问题 I get the data from rest api and I want to be rebuild Automatically again with any changes in the api and database and fetch new data please help me.. 来源： https://stackoverflow.com/questions/61301840/how-to-rebuild-my-gatsby-project-with-any-changes-in-the-api-and-database

问题 I don't understand the difference between basepath and path prefix in Gatsby , and when to use each feature Basepath: https://www.gatsbyjs.org/tutorial/part-seven/ Path prefix: https://www.gatsbyjs.org/docs/path-prefix/ 回答1: TL:DR pathPrefix has much more impact on your site — it add a prefix to the generated url of all your pages and assets. basePath is just a helper for generating slug from your filesystem — In my experience with Gatsby I rarely use it at all. pathPrefix It appends a prefix

问题 I don't understand the difference between basepath and path prefix in Gatsby , and when to use each feature Basepath: https://www.gatsbyjs.org/tutorial/part-seven/ Path prefix: https://www.gatsbyjs.org/docs/path-prefix/ 回答1: TL:DR pathPrefix has much more impact on your site — it add a prefix to the generated url of all your pages and assets. basePath is just a helper for generating slug from your filesystem — In my experience with Gatsby I rarely use it at all. pathPrefix It appends a prefix

问题 I don't understand the difference between basepath and path prefix in Gatsby , and when to use each feature Basepath: https://www.gatsbyjs.org/tutorial/part-seven/ Path prefix: https://www.gatsbyjs.org/docs/path-prefix/ 回答1: TL:DR pathPrefix has much more impact on your site — it add a prefix to the generated url of all your pages and assets. basePath is just a helper for generating slug from your filesystem — In my experience with Gatsby I rarely use it at all. pathPrefix It appends a prefix

问题 I've been experimenting with gatsby.js for a while and everything is going well except for this issue, i cannot include jQuery scripts unto the app so that it loads after the gatsby app has been rendered, i've the included script tags unto the html.js file and loaded it but it seems that the code is executed before react renders the content unto the screen i've tried using simple-load-script as well to include it on the componentDidMount method on the html.js app. But with no luck, here is