strapi / starters-and-templates Goto Github PK

View Code? Open in Web Editor NEW

316.0 316.0 114.0 14.84 MB

Monorepo for all official Strapi v4 templates

License: MIT License

CSS 1.69% JavaScript 98.31%

starters-and-templates's Introduction

Open-source headless CMS, self-hosted or Cloud you’re in control.

The leading open-source headless CMS, 100% JavaScript/TypeScript, flexible and fully customizable.

Cloud · Try live demo · Strapi 5 (coming soon)

Strapi Community Edition is a free and open-source headless CMS enabling you to manage any content, anywhere.

Self-hosted or Cloud: You can host and scale Strapi projects the way you want. You can save time by deploying to Strapi Cloud or deploy to the hosting platform you want**: AWS, Azure, Google Cloud, DigitalOcean.
Modern Admin Panel: Elegant, entirely customizable and a fully extensible admin panel.
Multi-database support: You can choose the database you prefer: PostgreSQL, MySQL, MariaDB, and SQLite.
Customizable: You can quickly build your logic by fully customizing APIs, routes, or plugins to fit your needs perfectly.
Blazing Fast and Robust: Built on top of Node.js and TypeScript, Strapi delivers reliable and solid performance.
Front-end Agnostic: Use any front-end framework (React, Next.js, Vue, Angular, etc.), mobile apps or even IoT.
Secure by default: Reusable policies, CORS, CSP, P3P, Xframe, XSS, and more.
Powerful CLI: Scaffold projects and APIs on the fly.

Getting Started

Read the Getting Started tutorial or follow the steps below:

⏳ Installation

Install Strapi with this Quickstart command to create a Strapi project instantly:

(Use yarn to install the Strapi project (recommended). Install yarn with these docs.)

yarn create strapi-app my-project --quickstart

(Use npm/npx to install the Strapi project.)

npx create-strapi-app my-project --quickstart

This command generates a brand new project with the default features (authentication, permissions, content management, content type builder & file upload). The Quickstart command installs Strapi using a SQLite database which is used for prototyping in development.

Enjoy 🎉

🖐 Requirements

Complete installation requirements can be found in the documentation under Installation Requirements.

Supported operating systems:

Ubuntu LTS/Debian 9.x
CentOS/RHEL 8
macOS Mojave
Windows 10
Docker

(Please note that Strapi may work on other operating systems, but these are not tested nor officially supported at this time.)

Node:

Strapi only supports maintenance and LTS versions of Node.js. Please refer to the Node.js release schedule for more information. NPM versions installed by default with Node.js are supported. Generally it's recommended to use yarn over npm where possible.

Strapi Version	Recommended	Minimum
4.14.5 and up	20.x	18.x
4.11.0 and up	18.x	16.x
4.3.9 to 4.10.x	18.x	14.x
4.0.x to 4.3.8	16.x	14.x

Database:

Database	Recommended	Minimum
MySQL	8.0	5.7.8
MariaDB	10.6	10.3
PostgreSQL	14.0	11.0
SQLite	3	3

We recommend always using the latest version of Strapi stable to start your new projects.

Features

Content Types Builder: Build the most flexible publishing experience for your content managers, by giving them the freedom to create any page on the go with fields, components and Dynamic Zones.
Media Library: Upload your images, videos, audio or documents to the media library. Easily find the right asset, edit and reuse it.
Internationalization: The Internationalization (i18n) plugin allows Strapi users to create, manage and distribute localized content in different languages, called "locales"
Role Based Access Control: Create an unlimited number of custom roles and permissions for admin and end users.
GraphQL or REST: Consume the API using REST or GraphQL

You can unlock additional features such as SSO, Audit Logs, Review Workflows in Strapi Cloud or Strapi Enterprise.

See more on our website.

Contributing

Please read our Contributing Guide before submitting a Pull Request to the project.

Community support

For general help using Strapi, please refer to the official Strapi documentation. For additional help, you can use one of these channels to ask a question:

Discord (For live discussion with the Community and Strapi team)
GitHub (Bug reports, Contributions)
Community Forum (Questions and Discussions)
Feedback section (Roadmap, Feature requests)
Twitter (Get the news fast)
Facebook
YouTube Channel (Learn from Video Tutorials)

Migration

Follow our migration guides on the documentation to keep your projects up-to-date.

Roadmap

Check out our roadmap to get informed of the latest features released and the upcoming ones. You may also give us insights and vote for a specific feature.

Documentation

See our dedicated repository for the Strapi documentation, or view our documentation live:

Try live demo

See for yourself what's under the hood by getting access to a hosted Strapi project with sample data.

License

See the LICENSE file for licensing information.

starters-and-templates's People

Contributors

Stargazers

Watchers

Forkers

teacherstrange initdc madmaxmehdi44 malgamves jlroche fury-101 angelolibero elegantstack rc-vast bankincity nikhil-shrestha lukejosten jpallard6120 julioduquejdk fecalemos agakadela software-trizzey lonnie-nguyen kzai ismailbouaddi chris-ycw s-you cally99 robzuar sosplbiz dlby ittp aryan109 kekewind t5k6 masonyekta fsefidabi govtp jrea-pn verofay polem mailyanyukan miguelt21 rawestmoreland jordan1022 chadwcarlson tesla0225 rortan134 kaeriraquel ayumi-oxd mlsokol wisdak-forks yurii-b-ma b8n4s8n okuyanet arthur-lama jasmines-human maxrh km1220 shammadahmed treciaks thelazron srishti3418 nickkang1 charlie-moon syeduali93 temakulakov themanfromearth1 fokion wizzer711 talkhot n1k0lay junghard-software kr1571nt fauxprophete bart-webleads littlebadbad coderstudio-dev devmostafanassar indranil-r ekimudzaki 0xgizmo samaregbesola midhun-phenomtec frikadellios vijaykhurana innoverset hungtrinhjh hypercoded shou67 prooftv sorokinvld kashika3101 jmccar lewisscally hunter-7010 nekonton cryptonahue orellanaed xiaoyu-nus adigiz dinosoeren edwardceballos ypradhan sergiolopezloya

starters-and-templates's Issues

Next-corporate Install fails @frontend unable to resolve dependency tree

Command used:
npx create-strapi-starter mysite3 next-corporate

Installing frontend dependencies
⠴ Installing dependencies:This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: Command failed with exit code 1: npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/next
npm ERR! next@"^11.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer next@"^8.1.1-canary.54 || ^9.0.0" from [email protected]
npm ERR! node_modules/next-seo
npm ERR! next-seo@"^4.7.1" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!

NextJS Blog Starter: React Dependency conflict

I tried to install the Blog starter with NextJs and Strapi but got the following error:

ERR! A complete log of this run can be found in: npm ERR! /Users/YOUR_USER/.npm/_logs/2023-02-19T09_43_45_854Z-debug-0.log This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: Error: Command failed with exit code 1: npm install npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: [email protected] npm ERR! Found: [email protected] npm ERR! node_modules/react npm ERR! react@"17.0.0" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer react@"^17.0.2" from [email protected] npm ERR! node_modules/next npm ERR! next@"^11.0.0" from the root project npm ERR! peer next@">=10.2.0" from [email protected] npm ERR! node_modules/eslint-config-next npm ERR! dev eslint-config-next@"^11.0.1" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. npm ERR! npm ERR! npm ERR! For a full report see: npm ERR! /Users/YOUR_USER/.npm/_logs/2023-02-19T09_43_45_854Z-eresolve-report.txt

It seems that that NextJs frontend requires a higher version of the React Package than the Strapi backend does.
I would suggest updating the dependencies, so that everything works again out of the box.

On Strapi Starters not working as intented

Hello 👋

I know a lot of you are having issues with working with Strapi Starters. I'm opening this to communicate that it is something we've noticed and are working on fixing the situation.

For a start we'll add this disclaimer to the repo as we're working on sunsetting the starters.

As you may have noticed, a lot of the Starters are out of date and given constraints in bandwidth and other priorities, we've decided to sunset all Starters and only actively maintain a single Next.js Starter.

We've updated most places that mention starters with this information and have unpublished most content that uses them. I'll share more updates here as we work on it. If you notice a place we might have missed please let us know below.

Thanks for your patience!

I'll add issues mentioning below so they're aware we're working on it.

#8 , #38 , #42 , #48 , #60 , #62 , #66 , #69, #73

Static HTML export fail (next export)

Hi,

I am struggling with next export on Strapi corporate template (with next.js). The thing is i18n is not compatible with next export and if I want to have free hosting on Heroku I just need it.

I've been trying to remove i18n package (and /fr/ data fetching) by myself but the app is a bit more complex than I can handle by myself. Is there a possibility to have a version with single language fetching? Or any article about deleting the package from your starters?

Thanks!

Strapi Starter Next Corporate Site - Error when creating new section

Using this starter.

I've followed the instructions to add a new section. It doesn't work - the new component will "render", but it receives no data other than the component name (__typename: "ComponentSectionsDuoContent").

My first instinct was that the query should be updated. So I updated the query in utils/api.js to include my new section. It now won't render anything, giving this error:

[develop:frontend] TypeError: Cannot destructure property 'metadata' of 'global.attributes' as it is undefined.
[develop:frontend]     at MyApp (webpack-internal:///./pages/_app.js:57:5)
[develop:frontend]     at processChild (/Users/tiagomota/Documents/Projects/Polar/polaramp-website/frontend/node_modules/react-dom/cjs/react-dom-server.node.development.js:3353:14)
[develop:frontend]     at resolve (/Users/tiagomota/Documents/Projects/Polar/polaramp-website/frontend/node_modules/react-dom/cjs/react-dom-server.node.development.js:3270:5)
[develop:frontend]     at ReactDOMServerRenderer.render (/Users/tiagomota/Documents/Projects/Polar/polaramp-website/frontend/node_modules/react-dom/cjs/react-dom-server.node.development.js:3753:22)
[develop:frontend]     at ReactDOMServerRenderer.read (/Users/tiagomota/Documents/Projects/Polar/polaramp-website/frontend/node_modules/react-dom/cjs/react-dom-server.node.development.js:3690:29)
[develop:frontend]     at renderToString (/Users/tiagomota/Documents/Projects/Polar/polaramp-website/frontend/node_modules/react-dom/cjs/react-dom-server.node.development.js:4298:27)
[develop:frontend]     at Object.renderPage (/Users/tiagomota/Documents/Projects/Polar/polaramp-website/frontend/node_modules/next/dist/next-server/server/render.js:53:854)
[develop:frontend]     at Function.getInitialProps (webpack-internal:///./node_modules/next/dist/pages/_document.js:211:19)
[develop:frontend]     at loadGetInitialProps (/Users/tiagomota/Documents/Projects/Polar/polaramp-website/frontend/node_modules/next/dist/next-server/lib/utils.js:5:101)
[develop:frontend]     at renderToHTML (/Users/tiagomota/Documents/Projects/Polar/polaramp-website/frontend/node_modules/next/dist/next-server/server/render.js:53:1145)

Steps to reproduce:

Create a new section following the guide here
At this point, the new component won't receive any data in the frontend other than it's own name, which doesn't help.
Add the new component to the query inside getPageData in utils/api.js, following the same structure as the existing sections in the query. The new query can even be an empty object, just ... on ComponentSectionsYourComponentName {}

Error when executing gatsby-blog starter

I just installed gatsby-blog starter and got some errors when the installation is concluded and the project starts automatically.

Running just the backend, all works properly, but when running the frontend, I got some errors.

Errors

➜  gatsby-blog git:(master) ✗ yarn develop
yarn run v1.22.19
$ cross-env FORCE_COLOR=1 npm-run-all -l -p develop:*
$ wait-on http://localhost:1337/admin && yarn --cwd frontend develop
$ yarn --cwd backend develop
$ strapi develop
[develop:backend ]
[develop:backend ]  Project information
[develop:backend ]
[develop:backend ] ┌────────────────────┬──────────────────────────────────────────────────┐
[develop:backend ] │ Time               │ Wed Jun 29 2022 22:41:59 GMT-0300 (Brasilia Sta… │
[develop:backend ] │ Launched in        │ 1069 ms                                          │
[develop:backend ] │ Environment        │ development                                      │
[develop:backend ] │ Process PID        │ 16832                                            │
[develop:backend ] │ Version            │ 4.2.2 (node v14.19.3)                            │
[develop:backend ] │ Edition            │ Community                                        │
[develop:backend ] └────────────────────┴──────────────────────────────────────────────────┘
[develop:backend ]
[develop:backend ]  Actions available
[develop:backend ]
[develop:backend ] One more thing...
[develop:backend ] Create your first administrator 💻 by going to the administration panel at:
[develop:backend ]
[develop:backend ] ┌─────────────────────────────┐
[develop:backend ] │ http://localhost:1337/admin │
[develop:backend ] └─────────────────────────────┘
[develop:backend ]
[develop:backend ] [2022-06-29 22:41:59.054] http: HEAD /admin (13 ms) 200
$ gatsby develop
[develop:backend ] [2022-06-29 22:41:59.791] http: GET /admin (5 ms) 200
[develop:backend ] [2022-06-29 22:41:59.976] http: GET /admin/project-type (2 ms) 200
[develop:backend ] [2022-06-29 22:42:00.121] http: GET /admin/init (2 ms) 200
[develop:frontend] success compile gatsby files - 0.619s
success load gatsby config - 0.015s
success load plugins - 0.503s
Loaded gatsby-source-strapi-plugin
success onPreInit - 0.005s
success initialize cache - 0.061s
success copy gatsby files - 0.086s
success Compiling Gatsby Functions - 0.148s
success onPreBootstrap - 0.166s
success createSchemaCustomization - 0.004s
[develop:frontend]
[develop:backend ] [2022-06-29 22:42:02.981] http: GET /api/content-type-builder/content-types (2 ms) 403

[develop:frontend]  ERROR #11321  PLUGIN
[develop:frontend]
[develop:frontend] "gatsby-source-strapi" threw an error while running the sourceNodes lifecycle:
[develop:frontend]
[develop:frontend] Request failed with status code 403
[develop:frontend]

[develop:frontend]
[develop:frontend]   Error: Request failed with status code 403
[develop:frontend]
[develop:frontend]   - createError.js:16 createError
[develop:frontend]     [frontend]/[axios]/lib/core/createError.js:16:15
[develop:frontend]
[develop:frontend]   - settle.js:17 settle
[develop:frontend]     [frontend]/[axios]/lib/core/settle.js:17:12
[develop:frontend]
[develop:frontend]   - http.js:293 IncomingMessage.handleStreamEnd
[develop:frontend]     [frontend]/[axios]/lib/adapters/http.js:293:11
[develop:frontend]
[develop:frontend]   - readable.js:1333 endReadableNT
[develop:frontend]     internal/streams/readable.js:1333:12
[develop:frontend]
[develop:frontend]   - task_queues.js:82 processTicksAndRejections
[develop:frontend]     internal/process/task_queues.js:82:21
[develop:frontend]
[develop:frontend]
warn The gatsby-source-strapi plugin has generated no Gatsby nodes. Do you need
[develop:frontend] it? This could also suggest the plugin is misconfigured.
success Checking for changed pages - 0.000s
success source and transform nodes - 0.088s
success building schema - 0.138s

[develop:frontend]  ERROR #85923  GRAPHQL
[develop:frontend]
[develop:frontend] There was an error in your GraphQL query:
[develop:frontend]
[develop:frontend] Cannot query field "allStrapiArticle" on type "Query".
[develop:frontend]
[develop:frontend] If you don't expect "allStrapiArticle" to exist on the type "Query" it is most
[develop:frontend] likely a typo. However, if you expect "allStrapiArticle" to exist there are a
[develop:frontend] couple of solutions to common problems:
[develop:frontend]
[develop:frontend] - If you added a new data source and/or changed something inside
[develop:frontend] gatsby-node/gatsby-config, please try a restart of your development server.
[develop:frontend] - You want to optionally use your field "allStrapiArticle" and right now it is
[develop:frontend] not used anywhere.
[develop:frontend]
[develop:frontend] It is recommended to explicitly type your GraphQL schema if you want to use
[develop:frontend] optional fields.
[develop:frontend]
[develop:frontend] File: gatsby-node.js:9:24
[develop:frontend]
[develop:frontend] See our docs page for more info on this error:
[develop:frontend] https://gatsby.dev/creating-type-definitions
[develop:frontend]

[develop:frontend]  ERROR
[develop:frontend]
[develop:frontend] There was an error loading your Strapi articles Cannot query field
[develop:frontend] "allStrapiArticle" on type "Query".
[develop:frontend]

[develop:frontend]
[develop:frontend]   GraphQLError: Cannot query field "allStrapiArticle" on type "Query".
[develop:frontend]
[develop:frontend]   - graphql-runner.ts:120 GraphQLRunner.validate
[develop:frontend]     [frontend]/[gatsby]/src/query/graphql-runner.ts:120:16
[develop:frontend]
[develop:frontend]   - graphql-runner.ts:187 GraphQLRunner.query
[develop:frontend]     [frontend]/[gatsby]/src/query/graphql-runner.ts:187:39
[develop:frontend]
[develop:frontend]   - create-graphql-runner.ts:57 apply
[develop:frontend]     [frontend]/[gatsby]/src/bootstrap/create-graphql-runner.ts:57:8
[develop:frontend]
[develop:frontend]   - create-pages.ts:36 wrappedGraphQL
[develop:frontend]     [frontend]/[gatsby]/src/services/create-pages.ts:36:47
[develop:frontend]
[develop:frontend]   - gatsby-node.js:9 Object.exports.createPages
[develop:frontend]     /home/marionbx/github/hubs/poc/gatsby-blog/frontend/gatsby-node.js:9:24
[develop:frontend]
[develop:frontend]   - api-runner-node.js:487 runAPI
[develop:frontend]     [frontend]/[gatsby]/src/utils/api-runner-node.js:487:22
[develop:frontend]
[develop:frontend]   - api-runner-node.js:638 Promise.catch.decorateEvent.pluginName
[develop:frontend]     [frontend]/[gatsby]/src/utils/api-runner-node.js:638:13
[develop:frontend]
[develop:frontend]   - debuggability.js:384 Promise._execute
[develop:frontend]     [frontend]/[bluebird]/js/release/debuggability.js:384:9
[develop:frontend]
[develop:frontend]   - promise.js:518 Promise._resolveFromExecutor
[develop:frontend]     [frontend]/[bluebird]/js/release/promise.js:518:18
[develop:frontend]
[develop:frontend]   - promise.js:103 new Promise
[develop:frontend]     [frontend]/[bluebird]/js/release/promise.js:103:10
[develop:frontend]
[develop:frontend]   - api-runner-node.js:636
[develop:frontend]     [frontend]/[gatsby]/src/utils/api-runner-node.js:636:16
[develop:frontend]
[develop:frontend]
failed createPages - 0.062s
success createPagesStatefully - 0.052s
info Total nodes: 37, SitePage nodes: 3 (use --verbose for breakdown)
success Checking for changed pages - 0.000s
success write out redirect data - 0.001s
success onPostBootstrap - 0.002s
info bootstrap finished - 3.385s
success onPreExtractQueries - 0.000s

[develop:frontend]  ERROR #85923  GRAPHQL
[develop:frontend]
[develop:frontend] There was an error in your GraphQL query:
[develop:frontend]
[develop:frontend] Cannot query field "strapiGlobal" on type "Query".
[develop:frontend]
[develop:frontend] If you don't expect "strapiGlobal" to exist on the type "Query" it is most
[develop:frontend] likely a typo. However, if you expect "strapiGlobal" to exist there are a couple
[develop:frontend]  of solutions to common problems:
[develop:frontend]
[develop:frontend] - If you added a new data source and/or changed something inside
[develop:frontend] gatsby-node/gatsby-config, please try a restart of your development server.
[develop:frontend] - You want to optionally use your field "strapiGlobal" and right now it is not
[develop:frontend] used anywhere.
[develop:frontend]
[develop:frontend] It is recommended to explicitly type your GraphQL schema if you want to use
[develop:frontend] optional fields.
[develop:frontend]
[develop:frontend] File: src/components/seo.js:8:7
[develop:frontend]
[develop:frontend] See our docs page for more info on this error:
[develop:frontend] https://gatsby.dev/creating-type-definitions
[develop:frontend]

[develop:frontend]  ERROR #85901  GRAPHQL
[develop:frontend]
[develop:frontend] There was an error in your GraphQL query:
[develop:frontend]
[develop:frontend] Unknown type "STRAPI__COMPONENT_SHARED_MEDIASTRAPI__COMPONENT_SHARED_QUOTESTRAPI
[develop:frontend] __COMPONENT_SHARED_RICH_TEXTSTRAPI__COMPONENT_SHARED_SLIDERUnion".
[develop:frontend]
[develop:frontend] GraphQL request:2:22
[develop:frontend] 2 |   fragment Blocks on
[develop:frontend] STRAPI__COMPONENT_SHARED_MEDIASTRAPI__COMPONENT_SHARED_QUOT
[develop:frontend]   |                      ^
[develop:frontend]   | ESTRAPI__COMPONENT_SHARED_RICH_TEXTSTRAPI__COMPONENT_SHARED_SLIDERUnion {
[develop:frontend]
[develop:frontend] File: src/pages/about.js:10:22
[develop:frontend]

[develop:frontend]
[develop:frontend]   GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_MEDIASTRAPI__COMPONENT_SH
[develop:frontend]   ARED_QUOTESTRAPI__COMPONENT_SHARED_RICH_TEXTSTRAPI__COMPONENT_SHARED_SLIDERUni
[develop:frontend]   on".
[develop:frontend]
[develop:frontend]   - query-compiler.js:365 processDefinitions
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:365:20
[develop:frontend]
[develop:frontend]   - query-compiler.js:176 processQueries
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:176:10
[develop:frontend]
[develop:frontend]   - query-compiler.js:78 compile
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:78:19
[develop:frontend]
[develop:frontend]   - query-watcher.ts:223 updateStateAndRunQueries
[develop:frontend]     [frontend]/[gatsby]/src/query/query-watcher.ts:223:40
[develop:frontend]
[develop:frontend]   - extract-queries.ts:18 extractQueries
[develop:frontend]     [frontend]/[gatsby]/src/services/extract-queries.ts:18:3
[develop:frontend]
[develop:frontend]

[develop:frontend]  ERROR #85901  GRAPHQL
[develop:frontend]
[develop:frontend] There was an error in your GraphQL query:
[develop:frontend]
[develop:frontend] Unknown type "STRAPI__COMPONENT_SHARED_RICH_TEXT".
[develop:frontend]
[develop:frontend] GraphQL request:4:12
[develop:frontend] 3 |     __typename
[develop:frontend] 4 |     ... on STRAPI__COMPONENT_SHARED_RICH_TEXT {
[develop:frontend]   |            ^
[develop:frontend] 5 |       richTextBody: body {
[develop:frontend]
[develop:frontend] File: src/pages/about.js:12:12
[develop:frontend]

[develop:frontend]
[develop:frontend]   GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_RICH_TEXT".
[develop:frontend]
[develop:frontend]   - query-compiler.js:365 processDefinitions
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:365:20
[develop:frontend]
[develop:frontend]   - query-compiler.js:176 processQueries
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:176:10
[develop:frontend]
[develop:frontend]   - query-compiler.js:78 compile
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:78:19
[develop:frontend]
[develop:frontend]   - query-watcher.ts:223 updateStateAndRunQueries
[develop:frontend]     [frontend]/[gatsby]/src/query/query-watcher.ts:223:40
[develop:frontend]
[develop:frontend]   - extract-queries.ts:18 extractQueries
[develop:frontend]     [frontend]/[gatsby]/src/services/extract-queries.ts:18:3
[develop:frontend]
[develop:frontend]

[develop:frontend]  ERROR #85901  GRAPHQL
[develop:frontend]
[develop:frontend] There was an error in your GraphQL query:
[develop:frontend]
[develop:frontend] Unknown type "STRAPI__COMPONENT_SHARED_MEDIA".
[develop:frontend]
[develop:frontend] GraphQL request:15:12
[develop:frontend] 14 |     }
[develop:frontend] 15 |     ... on STRAPI__COMPONENT_SHARED_MEDIA {
[develop:frontend]    |            ^
[develop:frontend] 16 |       file {
[develop:frontend]
[develop:frontend] File: src/pages/about.js:23:12
[develop:frontend]

[develop:frontend]
[develop:frontend]   GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_MEDIA".
[develop:frontend]
[develop:frontend]   - query-compiler.js:365 processDefinitions
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:365:20
[develop:frontend]
[develop:frontend]   - query-compiler.js:176 processQueries
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:176:10
[develop:frontend]
[develop:frontend]   - query-compiler.js:78 compile
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:78:19
[develop:frontend]
[develop:frontend]   - query-watcher.ts:223 updateStateAndRunQueries
[develop:frontend]     [frontend]/[gatsby]/src/query/query-watcher.ts:223:40
[develop:frontend]
[develop:frontend]   - extract-queries.ts:18 extractQueries
[develop:frontend]     [frontend]/[gatsby]/src/services/extract-queries.ts:18:3
[develop:frontend]
[develop:frontend]

[develop:frontend]  ERROR #85901  GRAPHQL
[develop:frontend]
[develop:frontend] There was an error in your GraphQL query:
[develop:frontend]
[develop:frontend] Unknown type "STRAPI__COMPONENT_SHARED_QUOTE".
[develop:frontend]
[develop:frontend] GraphQL request:25:12
[develop:frontend] 24 |     }
[develop:frontend] 25 |     ... on STRAPI__COMPONENT_SHARED_QUOTE {
[develop:frontend]    |            ^
[develop:frontend] 26 |       title
[develop:frontend]
[develop:frontend] File: src/pages/about.js:33:12
[develop:frontend]

[develop:frontend]
[develop:frontend]   GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_QUOTE".
[develop:frontend]
[develop:frontend]   - query-compiler.js:365 processDefinitions
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:365:20
[develop:frontend]
[develop:frontend]   - query-compiler.js:176 processQueries
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:176:10
[develop:frontend]
[develop:frontend]   - query-compiler.js:78 compile
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:78:19
[develop:frontend]
[develop:frontend]   - query-watcher.ts:223 updateStateAndRunQueries
[develop:frontend]     [frontend]/[gatsby]/src/query/query-watcher.ts:223:40
[develop:frontend]
[develop:frontend]   - extract-queries.ts:18 extractQueries
[develop:frontend]     [frontend]/[gatsby]/src/services/extract-queries.ts:18:3
[develop:frontend]
[develop:frontend]

[develop:frontend]  ERROR #85901  GRAPHQL
[develop:frontend]
[develop:frontend] There was an error in your GraphQL query:
[develop:frontend]
[develop:frontend] Unknown type "STRAPI__COMPONENT_SHARED_SLIDER".
[develop:frontend]
[develop:frontend] GraphQL request:29:12
[develop:frontend] 28 |     }
[develop:frontend] 29 |     ... on STRAPI__COMPONENT_SHARED_SLIDER {
[develop:frontend]    |            ^
[develop:frontend] 30 |       files {
[develop:frontend]
[develop:frontend] File: src/pages/about.js:37:12
[develop:frontend]

[develop:frontend]
[develop:frontend]   GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_SLIDER".
[develop:frontend]
[develop:frontend]   - query-compiler.js:365 processDefinitions
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:365:20
[develop:frontend]
[develop:frontend]   - query-compiler.js:176 processQueries
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:176:10
[develop:frontend]
[develop:frontend]   - query-compiler.js:78 compile
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:78:19
[develop:frontend]
[develop:frontend]   - query-watcher.ts:223 updateStateAndRunQueries
[develop:frontend]     [frontend]/[gatsby]/src/query/query-watcher.ts:223:40
[develop:frontend]
[develop:frontend]   - extract-queries.ts:18 extractQueries
[develop:frontend]     [frontend]/[gatsby]/src/services/extract-queries.ts:18:3
[develop:frontend]
[develop:frontend]

[develop:frontend]  ERROR #85923  GRAPHQL
[develop:frontend]
[develop:frontend] There was an error in your GraphQL query:
[develop:frontend]
[develop:frontend] Cannot query field "strapiAbout" on type "Query".
[develop:frontend]
[develop:frontend] If you don't expect "strapiAbout" to exist on the type "Query" it is most likely
[develop:frontend]  a typo. However, if you expect "strapiAbout" to exist there are a couple of
[develop:frontend] solutions to common problems:
[develop:frontend]
[develop:frontend] - If you added a new data source and/or changed something inside
[develop:frontend] gatsby-node/gatsby-config, please try a restart of your development server.
[develop:frontend] - You want to optionally use your field "strapiAbout" and right now it is not
[develop:frontend] used anywhere.
[develop:frontend]
[develop:frontend] It is recommended to explicitly type your GraphQL schema if you want to use
[develop:frontend] optional fields.
[develop:frontend]
[develop:frontend] File: src/pages/about.js:11:7
[develop:frontend]
[develop:frontend] See our docs page for more info on this error:
[develop:frontend] https://gatsby.dev/creating-type-definitions
[develop:frontend]

[develop:frontend]  ERROR #85901  GRAPHQL
[develop:frontend]
[develop:frontend] There was an error in your GraphQL query:
[develop:frontend]
[develop:frontend] Unknown type "STRAPI_ARTICLE".
[develop:frontend]
[develop:frontend] GraphQL request:2:27
[develop:frontend] 1 |
[develop:frontend] 2 |   fragment ArticleCard on STRAPI_ARTICLE {
[develop:frontend]   |                           ^
[develop:frontend] 3 |     id
[develop:frontend]
[develop:frontend] File: src/pages/index.js:10:27
[develop:frontend]

[develop:frontend]
[develop:frontend]   GraphQLError: Unknown type "STRAPI_ARTICLE".
[develop:frontend]
[develop:frontend]   - query-compiler.js:365 processDefinitions
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:365:20
[develop:frontend]
[develop:frontend]   - query-compiler.js:176 processQueries
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:176:10
[develop:frontend]
[develop:frontend]   - query-compiler.js:78 compile
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:78:19
[develop:frontend]
[develop:frontend]   - query-watcher.ts:223 updateStateAndRunQueries
[develop:frontend]     [frontend]/[gatsby]/src/query/query-watcher.ts:223:40
[develop:frontend]
[develop:frontend]   - extract-queries.ts:18 extractQueries
[develop:frontend]     [frontend]/[gatsby]/src/services/extract-queries.ts:18:3
[develop:frontend]
[develop:frontend]

[develop:frontend]  ERROR #85923  GRAPHQL
[develop:frontend]
[develop:frontend] There was an error in your GraphQL query:
[develop:frontend]
[develop:frontend] Cannot query field "allStrapiArticle" on type "Query".
[develop:frontend]
[develop:frontend] If you don't expect "allStrapiArticle" to exist on the type "Query" it is most
[develop:frontend] likely a typo. However, if you expect "allStrapiArticle" to exist there are a
[develop:frontend] couple of solutions to common problems:
[develop:frontend]
[develop:frontend] - If you added a new data source and/or changed something inside
[develop:frontend] gatsby-node/gatsby-config, please try a restart of your development server.
[develop:frontend] - You want to optionally use your field "allStrapiArticle" and right now it is
[develop:frontend] not used anywhere.
[develop:frontend]
[develop:frontend] It is recommended to explicitly type your GraphQL schema if you want to use
[develop:frontend] optional fields.
[develop:frontend]
[develop:frontend] File: src/pages/index.js:11:7
[develop:frontend]
[develop:frontend] See our docs page for more info on this error:
[develop:frontend] https://gatsby.dev/creating-type-definitions
[develop:frontend]

[develop:frontend]  ERROR #85923  GRAPHQL
[develop:frontend]
[develop:frontend] There was an error in your GraphQL query:
[develop:frontend]
[develop:frontend] Cannot query field "strapiGlobal" on type "Query".
[develop:frontend]
[develop:frontend] If you don't expect "strapiGlobal" to exist on the type "Query" it is most
[develop:frontend] likely a typo. However, if you expect "strapiGlobal" to exist there are a couple
[develop:frontend]  of solutions to common problems:
[develop:frontend]
[develop:frontend] - If you added a new data source and/or changed something inside
[develop:frontend] gatsby-node/gatsby-config, please try a restart of your development server.
[develop:frontend] - You want to optionally use your field "strapiGlobal" and right now it is not
[develop:frontend] used anywhere.
[develop:frontend]
[develop:frontend] It is recommended to explicitly type your GraphQL schema if you want to use
[develop:frontend] optional fields.
[develop:frontend]
[develop:frontend] File: src/pages/index.js:16:7
[develop:frontend]
[develop:frontend] See our docs page for more info on this error:
[develop:frontend] https://gatsby.dev/creating-type-definitions
[develop:frontend]

[develop:frontend]  ERROR #85901  GRAPHQL
[develop:frontend]
[develop:frontend] There was an error in your GraphQL query:
[develop:frontend]
[develop:frontend] Unknown type "STRAPI__COMPONENT_SHARED_MEDIASTRAPI__COMPONENT_SHARED_QUOTESTRAPI
[develop:frontend] __COMPONENT_SHARED_RICH_TEXTSTRAPI__COMPONENT_SHARED_SLIDERUnion".
[develop:frontend]
[develop:frontend] GraphQL request:2:22
[develop:frontend] 2 |   fragment Blocks on
[develop:frontend] STRAPI__COMPONENT_SHARED_MEDIASTRAPI__COMPONENT_SHARED_QUOT
[develop:frontend]   |                      ^
[develop:frontend]   | ESTRAPI__COMPONENT_SHARED_RICH_TEXTSTRAPI__COMPONENT_SHARED_SLIDERUnion {
[develop:frontend]
[develop:frontend] File: src/templates/article-post.js:37:22
[develop:frontend]

[develop:frontend]
[develop:frontend]   GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_MEDIASTRAPI__COMPONENT_SH
[develop:frontend]   ARED_QUOTESTRAPI__COMPONENT_SHARED_RICH_TEXTSTRAPI__COMPONENT_SHARED_SLIDERUni
[develop:frontend]   on".
[develop:frontend]
[develop:frontend]   - query-compiler.js:365 processDefinitions
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:365:20
[develop:frontend]
[develop:frontend]   - query-compiler.js:176 processQueries
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:176:10
[develop:frontend]
[develop:frontend]   - query-compiler.js:78 compile
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:78:19
[develop:frontend]
[develop:frontend]   - query-watcher.ts:223 updateStateAndRunQueries
[develop:frontend]     [frontend]/[gatsby]/src/query/query-watcher.ts:223:40
[develop:frontend]
[develop:frontend]   - extract-queries.ts:18 extractQueries
[develop:frontend]     [frontend]/[gatsby]/src/services/extract-queries.ts:18:3
[develop:frontend]
[develop:frontend]

[develop:frontend]  ERROR #85901  GRAPHQL
[develop:frontend]
[develop:frontend] There was an error in your GraphQL query:
[develop:frontend]
[develop:frontend] Unknown type "STRAPI__COMPONENT_SHARED_RICH_TEXT".
[develop:frontend]
[develop:frontend] GraphQL request:4:12
[develop:frontend] 3 |     __typename
[develop:frontend] 4 |     ... on STRAPI__COMPONENT_SHARED_RICH_TEXT {
[develop:frontend]   |            ^
[develop:frontend] 5 |       richTextBody: body {
[develop:frontend]
[develop:frontend] File: src/templates/article-post.js:39:12
[develop:frontend]

[develop:frontend]
[develop:frontend]   GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_RICH_TEXT".
[develop:frontend]
[develop:frontend]   - query-compiler.js:365 processDefinitions
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:365:20
[develop:frontend]
[develop:frontend]   - query-compiler.js:176 processQueries
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:176:10
[develop:frontend]
[develop:frontend]   - query-compiler.js:78 compile
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:78:19
[develop:frontend]
[develop:frontend]   - query-watcher.ts:223 updateStateAndRunQueries
[develop:frontend]     [frontend]/[gatsby]/src/query/query-watcher.ts:223:40
[develop:frontend]
[develop:frontend]   - extract-queries.ts:18 extractQueries
[develop:frontend]     [frontend]/[gatsby]/src/services/extract-queries.ts:18:3
[develop:frontend]
[develop:frontend]

[develop:frontend]  ERROR #85901  GRAPHQL
[develop:frontend]
[develop:frontend] There was an error in your GraphQL query:
[develop:frontend]
[develop:frontend] Unknown type "STRAPI__COMPONENT_SHARED_MEDIA".
[develop:frontend]
[develop:frontend] GraphQL request:15:12
[develop:frontend] 14 |     }
[develop:frontend] 15 |     ... on STRAPI__COMPONENT_SHARED_MEDIA {
[develop:frontend]    |            ^
[develop:frontend] 16 |       file {
[develop:frontend]
[develop:frontend] File: src/templates/article-post.js:50:12
[develop:frontend]

[develop:frontend]
[develop:frontend]   GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_MEDIA".
[develop:frontend]
[develop:frontend]   - query-compiler.js:365 processDefinitions
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:365:20
[develop:frontend]
[develop:frontend]   - query-compiler.js:176 processQueries
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:176:10
[develop:frontend]
[develop:frontend]   - query-compiler.js:78 compile
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:78:19
[develop:frontend]
[develop:frontend]   - query-watcher.ts:223 updateStateAndRunQueries
[develop:frontend]     [frontend]/[gatsby]/src/query/query-watcher.ts:223:40
[develop:frontend]
[develop:frontend]   - extract-queries.ts:18 extractQueries
[develop:frontend]     [frontend]/[gatsby]/src/services/extract-queries.ts:18:3
[develop:frontend]
[develop:frontend]

[develop:frontend]  ERROR #85901  GRAPHQL
[develop:frontend]
[develop:frontend] There was an error in your GraphQL query:
[develop:frontend]
[develop:frontend] Unknown type "STRAPI__COMPONENT_SHARED_QUOTE".
[develop:frontend]
[develop:frontend] GraphQL request:25:12
[develop:frontend] 24 |     }
[develop:frontend] 25 |     ... on STRAPI__COMPONENT_SHARED_QUOTE {
[develop:frontend]    |            ^
[develop:frontend] 26 |       title
[develop:frontend]
[develop:frontend] File: src/templates/article-post.js:60:12
[develop:frontend]

[develop:frontend]
[develop:frontend]   GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_QUOTE".
[develop:frontend]
[develop:frontend]   - query-compiler.js:365 processDefinitions
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:365:20
[develop:frontend]
[develop:frontend]   - query-compiler.js:176 processQueries
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:176:10
[develop:frontend]
[develop:frontend]   - query-compiler.js:78 compile
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:78:19
[develop:frontend]
[develop:frontend]   - query-watcher.ts:223 updateStateAndRunQueries
[develop:frontend]     [frontend]/[gatsby]/src/query/query-watcher.ts:223:40
[develop:frontend]
[develop:frontend]   - extract-queries.ts:18 extractQueries
[develop:frontend]     [frontend]/[gatsby]/src/services/extract-queries.ts:18:3
[develop:frontend]
[develop:frontend]

[develop:frontend]  ERROR #85901  GRAPHQL
[develop:frontend]
[develop:frontend] There was an error in your GraphQL query:
[develop:frontend]
[develop:frontend] Unknown type "STRAPI__COMPONENT_SHARED_SLIDER".
[develop:frontend]
[develop:frontend] GraphQL request:29:12
[develop:frontend] 28 |     }
[develop:frontend] 29 |     ... on STRAPI__COMPONENT_SHARED_SLIDER {
[develop:frontend]    |            ^
[develop:frontend] 30 |       files {
[develop:frontend]
[develop:frontend] File: src/templates/article-post.js:64:12
[develop:frontend]

[develop:frontend]
[develop:frontend]   GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_SLIDER".
[develop:frontend]
[develop:frontend]   - query-compiler.js:365 processDefinitions
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:365:20
[develop:frontend]
[develop:frontend]   - query-compiler.js:176 processQueries
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:176:10
[develop:frontend]
[develop:frontend]   - query-compiler.js:78 compile
[develop:frontend]     [frontend]/[gatsby]/src/query/query-compiler.js:78:19
[develop:frontend]
[develop:frontend]   - query-watcher.ts:223 updateStateAndRunQueries
[develop:frontend]     [frontend]/[gatsby]/src/query/query-watcher.ts:223:40
[develop:frontend]
[develop:frontend]   - extract-queries.ts:18 extractQueries
[develop:frontend]     [frontend]/[gatsby]/src/services/extract-queries.ts:18:3
[develop:frontend]
[develop:frontend]

[develop:frontend]  ERROR #85923  GRAPHQL
[develop:frontend]
[develop:frontend] There was an error in your GraphQL query:
[develop:frontend]
[develop:frontend] Cannot query field "strapiArticle" on type "Query".
[develop:frontend]
[develop:frontend] If you don't expect "strapiArticle" to exist on the type "Query" it is most
[develop:frontend] likely a typo. However, if you expect "strapiArticle" to exist there are a
[develop:frontend] couple of solutions to common problems:
[develop:frontend]
[develop:frontend] - If you added a new data source and/or changed something inside
[develop:frontend] gatsby-node/gatsby-config, please try a restart of your development server.
[develop:frontend] - You want to optionally use your field "strapiArticle" and right now it is not
[develop:frontend] used anywhere.
[develop:frontend]
[develop:frontend] It is recommended to explicitly type your GraphQL schema if you want to use
[develop:frontend] optional fields.
[develop:frontend]
[develop:frontend] File: src/templates/article-post.js:38:5
[develop:frontend]
[develop:frontend] See our docs page for more info on this error:
[develop:frontend] https://gatsby.dev/creating-type-definitions
[develop:frontend]
failed extract queries from components - 1.321s
success write out requires - 0.004s
success run page queries - 0.008s - 1/1 122.44/s

[develop:frontend]  ERROR
[develop:frontend]
[develop:frontend] Module not found: Error: Can't resolve
[develop:frontend] '../../public/page-data/sq/d/4175596634.json' in
[develop:frontend] '/home/marionbx/github/hubs/poc/gatsby-blog/frontend/src/components'
[develop:frontend]

[develop:frontend]
[develop:frontend]   ModuleNotFoundError: Module not found: Error: Can't resolve '../../public/page
[develop:frontend]   -data/sq/d/4175596634.json' in '/home/marionbx/github/hubs/poc/gatsby-blog/fro
[develop:frontend]   ntend/src/components'
[develop:frontend]
[develop:frontend]   - Compilation.js:2016
[develop:frontend]     [frontend]/[webpack]/lib/Compilation.js:2016:28
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:798
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:798:13
[develop:frontend]
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:270
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:270:22
[develop:frontend]
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:434
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:434:22
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:116
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:116:11
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:670
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:670:25
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:855
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:855:8
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:975
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:975:5
[develop:frontend]
[develop:frontend]   - async.js:6883
[develop:frontend]     [frontend]/[neo-async]/async.js:6883:13
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:950 Array.<anonymous>
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:950:14
[develop:frontend]
[develop:frontend]   - async.js:2517 arrayEachFunc
[develop:frontend]     [frontend]/[neo-async]/async.js:2517:19
[develop:frontend]
[develop:frontend]   - async.js:6858 Object.parallel
[develop:frontend]     [frontend]/[neo-async]/async.js:6858:9
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:873 NormalModuleFactory._resolveResourceErrorHints
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:873:12
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:834
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:834:18
[develop:frontend]
[develop:frontend]

[develop:frontend]  ERROR
[develop:frontend]
[develop:frontend] Module not found: Error: Can't resolve
[develop:frontend] '../../public/page-data/sq/d/3105690032.json' in
[develop:frontend] '/home/marionbx/github/hubs/poc/gatsby-blog/frontend/src/pages'
[develop:frontend]

[develop:frontend]
[develop:frontend]   ModuleNotFoundError: Module not found: Error: Can't resolve '../../public/page
[develop:frontend]   -data/sq/d/3105690032.json' in '/home/marionbx/github/hubs/poc/gatsby-blog/fro
[develop:frontend]   ntend/src/pages'
[develop:frontend]
[develop:frontend]   - Compilation.js:2016
[develop:frontend]     [frontend]/[webpack]/lib/Compilation.js:2016:28
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:798
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:798:13
[develop:frontend]
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:270
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:270:22
[develop:frontend]
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:434
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:434:22
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:116
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:116:11
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:670
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:670:25
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:855
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:855:8
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:975
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:975:5
[develop:frontend]
[develop:frontend]   - async.js:6883
[develop:frontend]     [frontend]/[neo-async]/async.js:6883:13
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:950 Array.<anonymous>
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:950:14
[develop:frontend]
[develop:frontend]   - async.js:2517 arrayEachFunc
[develop:frontend]     [frontend]/[neo-async]/async.js:2517:19
[develop:frontend]
[develop:frontend]   - async.js:6858 Object.parallel
[develop:frontend]     [frontend]/[neo-async]/async.js:6858:9
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:873 NormalModuleFactory._resolveResourceErrorHints
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:873:12
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:834
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:834:18
[develop:frontend]
[develop:frontend]

[develop:frontend]  ERROR
[develop:frontend]
[develop:frontend] Module not found: Error: Can't resolve
[develop:frontend] '../../public/page-data/sq/d/960431041.json' in
[develop:frontend] '/home/marionbx/github/hubs/poc/gatsby-blog/frontend/src/pages'
[develop:frontend]

[develop:frontend]
[develop:frontend]   ModuleNotFoundError: Module not found: Error: Can't resolve '../../public/page
[develop:frontend]   -data/sq/d/960431041.json' in '/home/marionbx/github/hubs/poc/gatsby-blog/fron
[develop:frontend]   tend/src/pages'
[develop:frontend]
[develop:frontend]   - Compilation.js:2016
[develop:frontend]     [frontend]/[webpack]/lib/Compilation.js:2016:28
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:798
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:798:13
[develop:frontend]
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:270
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:270:22
[develop:frontend]
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:434
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:434:22
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:116
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:116:11
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:670
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:670:25
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:855
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:855:8
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:975
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:975:5
[develop:frontend]
[develop:frontend]   - async.js:6883
[develop:frontend]     [frontend]/[neo-async]/async.js:6883:13
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:950 Array.<anonymous>
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:950:14
[develop:frontend]
[develop:frontend]   - async.js:2517 arrayEachFunc
[develop:frontend]     [frontend]/[neo-async]/async.js:2517:19
[develop:frontend]
[develop:frontend]   - async.js:6858 Object.parallel
[develop:frontend]     [frontend]/[neo-async]/async.js:6858:9
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:873 NormalModuleFactory._resolveResourceErrorHints
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:873:12
[develop:frontend]
[develop:frontend]   - NormalModuleFactory.js:834
[develop:frontend]     [frontend]/[webpack]/lib/NormalModuleFactory.js:834:18
[develop:frontend]
[develop:frontend]
not finished Building development bundle - 1.526s
[develop:frontend]
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ERROR: "develop:frontend" exited with 1.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
➜  gatsby-blog git:(master) ✗

Steps to reproduce

Install Strapi/Gatsby Starter using yarn create strapi-starter my-project gatsby-blog
Wait until it install and execute automatically
If it not execute automatically when installation is finished, just run yarn develop on my-project folder.

Version

Npm: 6.14.17
Node: 14.19.3
Yarn: 1.22.19
Frontend dependencies:

  "dependencies": {
    "gatsby": "^4.6.1",
    "gatsby-plugin-gatsby-cloud": "^4.7.0",
    "gatsby-plugin-image": "^2.6.0",
    "gatsby-plugin-postcss": "^5.6.0",
    "gatsby-plugin-sharp": "^4.6.0",
    "gatsby-source-strapi": "^2.0.0",
    "gatsby-transformer-remark": "^5.6.0",
    "gatsby-transformer-sharp": "^4.6.0",
    "postcss": "^8.4.6",
    "react": "^17.0.1",
    "react-dom": "^17.0.1",
    "react-helmet": "^6.1.0",
    "react-slick": "^0.28.1",
    "slick-carousel": "^1.8.1"
  },
  "devDependencies": {
    "@tailwindcss/line-clamp": "^0.3.1",
    "@tailwindcss/typography": "^0.5.1",
    "autoprefixer": "^10.4.2",
    "eslint": "^8.8.0",
    "eslint-config-prettier": "^8.3.0",
    "eslint-config-react-app": "^7.0.0",
    "eslint-plugin-prettier": "^4.0.0",
    "prettier": "^2.5.1",
    "prettier-plugin-tailwindcss": "^0.1.4",
    "tailwindcss": "^3.0.18"
  }

TypeError: Cannot destructure property 'metadata' of 'global.attributes'

This error occurs if you set a slug to the "Content-Manager" -> "Home" -> "slug" and afterwards re-empty this field.

Peer Dependency error, failed install

I believe the starter is installing the v3 template: https://github.com/strapi/strapi-template-corporate

Not the v4 template 'corporate' in this repo.

My error is,

C:\Users\raine\source\repos\nextStrapi2>npx create-strapi-starter qms-project next-corporate
? Choose your installation type Quickstart (recommended)
Installing @strapi/starter-next-corporate starter.
Creating a quickstart project.
Creating a new Strapi application at C:\Users\raine\source\repos\nextStrapi2\qms-project\backend.
Creating files.
Installing @strapi/template-corporate template.
Dependencies installed successfully.

Your application was created at C:\Users\raine\source\repos\nextStrapi2\qms-project\backend.

Available commands in your project:

  npm run develop
  Start Strapi in watch mode. (Changes in Strapi project files will trigger a server restart)

  npm run start
  Start Strapi without watch mode.

  npm run build
  Build Strapi admin panel.

  npm run strapi
  Display all available commands.

You can start by doing:

  cd C:\Users\raine\source\repos\nextStrapi2\qms-project\backend
  npm run develop

Creating Strapi starter frontend at C:\Users\raine\source\repos\nextStrapi2\qms-project\frontend.
Installing frontend dependencies
- Installing dependencies:  See C:\Users\raine\AppData\Local\npm-cache\eresolve-report.txt for a full report. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: Command failed with exit code 1: npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/next
npm ERR!   next@"^11.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer next@"^8.1.1-canary.54 || ^9.0.0" from [email protected]
npm ERR! node_modules/next-seo
npm ERR!   next-seo@"^4.7.1" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See C:\Users\raine\AppData\Local\npm-cache\eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\raine\AppData\Local\npm-cache\_logs\2022-02-03T01_46_05_091Z-debug.log
    at makeError (C:\Users\raine\AppData\Local\npm-cache\_npx\ecd569b0a81a6814\node_modules\execa\lib\error.js:60:11)
    at handlePromise (C:\Users\raine\AppData\Local\npm-cache\_npx\ecd569b0a81a6814\node_modules\execa\index.js:118:26)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async installWithLogs (C:\Users\raine\AppData\Local\npm-cache\_npx\ecd569b0a81a6814\node_modules\create-strapi-starter\utils\build-starter.js:85:3)
    at async buildStarter (C:\Users\raine\AppData\Local\npm-cache\_npx\ecd569b0a81a6814\node_modules\create-strapi-starter\utils\build-starter.js:181:3)
| Installing dependencies:  npm ERR! A complete log of this run can be found in: npm ERR!     C:\Users\raine\AppData\Local\npm-cache\_logs\2022-02-03T01_46_05_091Z-debug.log

Unable to deploy the starter on aws

Hi, I'm having issues setting this starter up on aws.
I've created and EC2 instance with Amazon 2
Installed, git, nvm, npm, yarn & node on the instance.
Then yarn install.

Usually on local I would run yarn develop on the main directory that has both frontend and backend.

Unfortunately strapi isn't recognising the command.
With npm install strapi and trying again same issue.

I think there's an issue with yarn which this project is set up on ec2 Amazon 2 servers.
Nvm use 14.19.1 is my version.

Does anyone know what compat issues there are for deploying on aws?

Has anyone and updated script to add to the repo?
Or faced same issue?

Thanks

Bug in lead-form.js : JSON data sent to server is malformed

Email lead form submissions fail in the Corporate Starter Template because the JSON data sent to http://localhost:1337/api/lead-form-submissions isn't wrapped in { data: { <payload> }}, leading to 400 BAD REQUEST errors.

Buggy code:

await fetchAPI(
	"/lead-form-submissions",
	{},
	{
		method: "POST",
		body: JSON.stringify({
			email: values.email,
			location: data.location,
		}),
	}
)

Fixed code:

await fetchAPI(
	"/lead-form-submissions",
	{},
	{
		method: "POST",
		body: JSON.stringify({
			data: {
				email: values.email,
				location: data.location,
			}
		}),
	}
)

At first I couldn't replicate this behavior with Postman either. Turns out Strapi expects its POSTDATA in a very peculiar way (at least peculiar to me 😂).

Mad props to Arsiki at https://stackoverflow.com/questions/71187083/problem-with-post-action-on-strapi-via-postman for figuring out how to send POSTDATA to Strapi via Postman. (I am sure the proper way is documented somewhere also.)

After that, it became clear that the data field was missing in the JSON submitted back home via the lead form.

Typescript support with Strapi 4.2?

Hello,

is there any plans to migrate the actual starter to Strapi 4.2 for Typescript support?

Thanks!

v4 proposal for nuxt-e-commerce

Hello

I have some customized code for one-click installation

git clone https://github.com/akaJes/nuxt-e-commerce.git
yarn create strapi-starter tester ./nuxt-e-commerce/

It possible to add it to the common v4 templates?

Thanks

support for multiple pictures per post in media gallery

Enabling multiple images mode in the media gallery produces the following error:
open:

Server Error
TypeError: Cannot destructure property 'url' of 'image.data.attributes' as it is undefined.

This error happened while generating the page. Any console logs will be displayed in the terminal window.
Source
components/image.js (5:10) @ Image


  3 | 
  4 | const Image = ({ image, style }) => {
> 5 |   const { url, alternativeText, width, height } = image.data.attributes

next-ecommerce: HTTP ERROR 426

I tried using npx create-strapi-app my-app-name --template ecommerce to create a new project, eveything worked fine except when it redirect me to create my admin account, I have an http error 426.

I am using npm and Node.js v20.11.1.

Could someone help me ?

Worth sunsetting these monorepos?

There's many issues using these templates and I've spent countless hours trying to use these as boilerplates.
Two many strange errors with cors. Eccon refused both on dev and production. It's much better to have templates which are separated.

yarn develop using one monorepo package never works. Sometimes you need to time this and start the backend first.

In CI CD the problems redeploying features ends up taking so much time to debug weird quirks.

Please stick with using well maintained separated front and backend templates.

This way it's easier to maintain and will cause less github issues

Gatsby Blog starter fails frontend

Both approaches outlined in the doc for running the start successfully build and start the backend but fail to build the frontend.

OSX 12.1

node -v
v16.14.2

yarn -v
1.22.18

NPX output
npx.txt

YARN output
yarn.txt

The Next Blog starter works fine with either approach

Are the starters working with V4 ? (problem with at least next-corporate)

Bug report

Describe the bug

The next-corporate starter does not work :

Error on start
Error on http://localhost:3000

Steps to reproduce the behavior

create project with starter yarn create strapi-starter my-project next-corporate
error in logs : TypeError: Cannot destructure property 'attributes' of 'strapi.getModel(...)' as it is undefined. ...
go to admin and create first login/password
go to to http://localhost:3000
here is a nice error see

Expected behavior

starter to work without error in log or in front

System

Node.js version: LTS 16
yarn
Strapi version: 4
Database:
Operating system: MacOS Monterey

Strapi Starter Gatsby Corporate Site (V4) status

Hi Remi (and others),

I have a few questions about your Strapi Starter Gatsby Corporate Site (V4) starter (https://github.com/strapi/starters-and-templates/tree/main/packages/starters/gatsby-corporate):

Do you have any idea when this starter for Strapi V4 will become available? I like the version for Strapi V3 a lot so I'm quite interested in the Strapi V4 version!
Will the functionality of the V4 starter remain the same or will it offer more? (eg. fetching Strapi Dynamic Zone data and implementing the Strapi SEO plugin)

Thanks for the great work on Strapi!

Best regards,
Jacco van den Berg

Custom starter with mysql seems broken

Short summary

Running the strapi-starter together with gatsby-blog and custom setup seems to not function properly.

Steps to reproduce

Run yarn create strapi-starter my-project gatsby-blog
Choose custom installation with manual settings
Choose TypeScript
Choose mysql
Choose correct mysql settings (make sure the provided database exists and user has appropriate permissions)

This seems to work fine, but upon starting the Gatsby application there are numerous errors related to graphql and permissions. And opening the Strapi UI also shows some issues, where for example the default content is missing. The permission settings for the template's starter-type are also missing in the UI.

next-corporate: preview is broken

The preview mode fails on next-corporate.
The issue comes from packages/starters/next-corporate/starter/pages/api/preview.js L15, where the locale variable isn't defined.

How to add multiple tags in a single blog

Hello Strapi, I am really sorry to put this as an issue. I have posted it in Stackoverflow also. Actually I want to implement something and not able to figure it out so I am posting it here for some help.
In the Next + Strapi there is an option to categorize blogs based on category however I would like to add multiple tags to a single blog and in my Next app I would like to categorize them based on these tags and View all. I have create a Tag collection type and tried to establish a relation however I am not getting it in API response. Do I need to modify something related to API call in my Next app.

Next.js blog: Error: An error occured please try again

Newly created app just doesn't work. API throw 404 error for global endpoint.

Possible issue: the OOTB content types are not visible in Roles -> permissions.

Spend too much time on this. Do not use those templates...

Bug when creating strapi project with template + TypeScript

I just created a strapi project using the Blog template and also added the --ts flag so typescript is enabled.
However: strapi won't recognize the collections etc. in the roles section in the template since they are .js files and not .ts.
Result: you can create collections that are created by the template like 'article', but when calling the rest api or checking permissions in the admin panel the collection is not shown.
Results in this error:

{
  data: null,
  error: {
    status: 404,
    name: 'NotFoundError',
    message: 'Not Found',
    details: {}
  }
}

when calling e.g. this rest api:
GET http://localhost:1337/api/articles

Starter next-corporate with TypeScript: backend server not able to start due to TypeError

Description

Running the starter command yarn create strapi-starter my-site next-corporate and picking the options "Custom" and "TypeScript", leads to error: Cannot read properties of undefined (reading 'routes'), so the backend server isn't able to start.

Option "Quickstart" (JavaScript) does work.

Steps to reproduce + outputs

Use latest node 16 LTS

~/strapi-next-corporate-starter-test$ nvm use 16
Now using node v16.17.0 (npm v8.15.0)

Run Starter command

> Custom (manual settings)
> TypeScript
> sqlite

  ~/strapi-next-corporate-starter-test$ yarn create strapi-starter my-site next-corporate
  yarn create v1.22.15
  [1/4] Resolving packages...
  [2/4] Fetching packages...
  [3/4] Linking dependencies...
  [4/4] Building fresh packages...
  success Installed "[email protected]" with binaries:
        - create-strapi-starter
  ? Choose your installation type Custom (manual settings)
  Installing @strapi/starter-next-corporate starter.
  ? Choose your preferred language TypeScript
  ? Choose your default database client sqlite
  ? Filename: .tmp/data.db
  
  Creating a project with custom database options.
  Creating a new Strapi application at /home/falk/strapi-next-corporate-starter-test/my-site/backend.
  Creating files.
  Installing @strapi/template-corporate template.
  Dependencies installed successfully.
  
  Your application was created at /home/falk/strapi-next-corporate-starter-test/my-site/backend.
  
  Available commands in your project:
  
    yarn develop
    Start Strapi in watch mode. (Changes in Strapi project files will trigger a server restart)
  
    yarn start
    Start Strapi without watch mode.
  
    yarn build
    Build Strapi admin panel.
  
    yarn strapi
    Display all available commands.
  
  You can start by doing:
  
    cd /home/falk/strapi-next-corporate-starter-test/my-site/backend
    yarn develop
  
  Creating Strapi starter frontend at /home/falk/strapi-next-corporate-starter-test/my-site/frontend.
  Installing frontend dependencies
  Dependencies installed successfully.
  Dependencies installed successfully.
  Starting the app
  yarn run v1.22.15
  $ cross-env FORCE_COLOR=1 npm-run-all -l -p develop:*
  $ wait-on http://localhost:1337/admin && yarn --cwd frontend develop
  $ yarn --cwd backend develop
  $ strapi develop
  [develop:backend ] Starting the compilation for TypeScript files in /home/falk/strapi-next-corporate-starter-test/my-site/backend
  [develop:backend ] Building your admin UI with development configuration...
  [develop:backend ] ℹ Compiling Webpack
  [develop:backend ] ✔ Webpack: Compiled successfully in 11.23s
  [develop:backend ] Admin UI built successfully
  [develop:backend ] [2022-08-31 11:27:38.773] debug: ⛔️ Server wasn't able to start properly.
  [develop:backend ] [2022-08-31 11:27:38.774] error: Cannot read properties of undefined (reading 'routes')
  [develop:backend ] TypeError: Cannot read properties of undefined (reading 'routes')
  [develop:backend ]     at Object.addCreateLocalizationAction (/home/falk/strapi-next-corporate-starter-test/my-site/backend/node_modules/@strapi/plugin-i18n/server/services/core-api.js:184:41)
  [develop:backend ]     at /home/falk/strapi-next-corporate-starter-test/my-site/backend/node_modules/@strapi/plugin-i18n/server/register.js:78:22
  [develop:backend ]     at Array.forEach (<anonymous>)
  [develop:backend ]     at extendLocalizedContentTypes (/home/falk/strapi-next-corporate-starter-test/my-site/backend/node_modules/@strapi/plugin-i18n/server/register.js:56:38)
  [develop:backend ]     at Object.module.exports [as register] (/home/falk/strapi-next-corporate-starter-test/my-site/backend/node_modules/@strapi/plugin-i18n/server/register.js:12:3)
  [develop:backend ]     at Object.register (/home/falk/strapi-next-corporate-starter-test/my-site/backend/node_modules/@strapi/strapi/lib/core/domain/module/index.js:47:46)
  [develop:backend ]     at Object.register (/home/falk/strapi-next-corporate-starter-test/my-site/backend/node_modules/@strapi/strapi/lib/core/registries/modules.js:33:19)
  [develop:backend ]     at async Strapi.runLifecyclesFunctions (/home/falk/strapi-next-corporate-starter-test/my-site/backend/node_modules/@strapi/strapi/lib/Strapi.js:510:5)
  [develop:backend ]     at async Strapi.register (/home/falk/strapi-next-corporate-starter-test/my-site/backend/node_modules/@strapi/strapi/lib/Strapi.js:379:5)
  [develop:backend ]     at async Strapi.load (/home/falk/strapi-next-corporate-starter-test/my-site/backend/node_modules/@strapi/strapi/lib/Strapi.js:456:5)
  error Command failed with exit code 1.
  info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
  error Command failed with exit code 1.
  info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
  ERROR: "develop:backend" exited with 1.
  error Command failed with exit code 1.
  info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
  This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
  Error: Command failed with exit code 1: yarn develop
      at makeError (/home/falk/.config/yarn/global/node_modules/execa/lib/error.js:60:11)
      at handlePromise (/home/falk/.config/yarn/global/node_modules/execa/index.js:118:26)
      at processTicksAndRejections (node:internal/process/task_queues:96:5)
      at async buildStarter (/home/falk/.config/yarn/global/node_modules/create-strapi-starter/utils/build-starter.js:194:3)
  Done in 200.17s.

Installation failing with node v17

Hi, I got the following error when installing the Starter:

npx create-strapi-starter my-project gatsby-blog

Resulting in:

Error while installing dependencies:
error [email protected]: The engine "node" is incompatible with this module. Expected version ">=12.x.x <=16.x.x". Got "17.3.0"
error Found incompatible module.

Seems like the Starter is not compatible with node > 16. Maybe it would help to provide a Dockerfile with the suitable environment.

Environment: Apple Silicone M1

Strapi Starter Next Blog: neverending 'Creating an optimized production build'

Hi!

I have a neverending 'Creating an optimized production build' bug when trying to build the project. It builds right after fresh install, but it freezes for the second and subsequent times.

node version is 16.14.2
It is most likely a next.js issue.

nextjs installed and started with error

Unoptimized image request for blur placeholder

I encountered an issue regarding the Strapi Starter Next Blog, but is most likely relevant to all Strapi starters and templates.
When the blur placeholder prop is added to the Next Image component in frontend\components\image.js, the optimizations that Next does relating to the image get nullified. This is the case, because the optimized and unoptimized version of the image are then both fetched. This can be witnessed in the Network tab of the developer tools.

For clarification, if these two lines of code are added the raw and optimized version of the Strapi image are requested:

placeholder={"blur"}
blurDataURL={getStrapiMedia(image)}

Full code of frontend\components\image.js:

import { getStrapiMedia } from "../lib/media"
import NextImage from "next/image"

const Image = ({ image, style }) => {
  const { url, alternativeText, width, height } = image.data.attributes

  // const loader = () => {
  //   return getStrapiMedia(image)
  // }

  return (
    <NextImage
      // loader={loader}
      layout="responsive"
      width={width || "100%"}
      height={height || "100%"}
      objectFit="contain"
      src={getStrapiMedia(image)}
      alt={alternativeText || ""}
      placeholder={"blur"}
      blurDataURL={getStrapiMedia(image)}
    />
  )
}

export default Image

Frontend fails with Type error after first install and run next-corportate

Hey, I followed the steps in docs and installed everything successfully. After running both frontend and backend, the backend works correctly but the frontend throws a type error. I saw graphql response statuses are 400 on the logs.
I did not do anything except installation steps in docs.

The related starter is next-corportate

FetchAPI error when deploying Strapi Next.js blog

Hello!

Everything runs smoothly in my development environment (when I run yarn dev). And I can even run yarn run build on my local computer with no problems. I successfully deployed Strapi to Heroku, and that works well. Now, my only problem occurs when deploying the next.js blog to Vercel.

I receive an error with fetchAPI, and I'm curious if anyone else has gotten the same error, attached here.

From what I've seen on Stack Overflow, you're not supposed to fetch an API route directly from getStaticProps or getStaticPaths, but I don't think we're doing that... aren't we using a helper function fetchAPI in order to not do it directly?

If anyone has had this problem or solved it please let me know!

404 -> Unhandled Runtime Error Error: Failed to load static props

Dear Strapi,

I did a clean install of the starter both with npm and yarn and I keep getting all sorts of issues:
This time, I tried several versions of Node including this time 16.0.0.
After a 1 second 404 error, the frontend changes to the following error:

Unhandled Runtime Error
Error: Failed to load static props

Call Stack
eval
node_modules/next/dist/next-server/lib/router/router.js (43:281)

The backend does not have any data from the front end in it and it is a fresh admin. I always used the recommended settings.
I have this in Strapi version 3 but it is a shame to go back...

v4 Strapi - next-corportate and blog fails with custom

I tried this on Strapi v3 and it works perfectly for Postgres and Mysql.
Strapi v4 manual with Mysql and Postgres fails.
+++++++++++++++++++++++++++++++++++++++
❯ yarn create strapi-starter backend-strapi4 next-corporate
yarn create v1.22.17
warning package.json: No license field
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Installed "[email protected]" with binaries:
- create-strapi-starter
? Choose your installation type Custom (manual settings)
Installing @strapi/starter-next-corporate starter.
? Choose your default database client mysql
? Database name: st-strapi4
? Host: 127.0.0.1
? Port: 3306
? Username: admin
? Password: ***********
? Enable SSL connection: No

Creating a project with custom database options.
Creating a new Strapi application at /home/xxxxx/dev/sts/backend-strapi4/backend.
Creating files.
Installing @strapi/template-corporate template.
Dependencies installed successfully.

Your application was created at /home/xxxxx/dev/sts/backend-strapi4/backend.

Available commands in your project:

yarn develop
Start Strapi in watch mode. (Changes in Strapi project files will trigger a server restart)

yarn start
Start Strapi without watch mode.

yarn build
Build Strapi admin panel.

yarn strapi
Display all available commands.

You can start by doing:

cd /home/xxxx/dev/sts/backend-strapi4/backend
yarn develop

Creating Strapi starter frontend at /home/xxxxx/dev/sts/backend-strapi4/frontend.
Installing frontend dependencies
Dependencies installed successfully.
Dependencies installed successfully.
Starting the app
yarn run v1.22.17
warning ../../../package.json: No license field
$ cross-env FORCE_COLOR=1 npm-run-all -l -p develop:*
warning ../../../package.json: No license field
warning ../../../package.json: No license field
$ wait-on http://localhost:1337/admin && yarn --cwd frontend develop
$ yarn --cwd backend develop
warning ../../../../package.json: No license field
$ strapi develop
[develop:backend ] Building your admin UI with development configuration ...
[develop:backend ] ℹ Compiling Webpack
[develop:backend ] ✔ Webpack: Compiled successfully in 18.58s
[develop:backend ] Admin UI built successfully
[develop:backend ] [2021-12-28 02:53:44.582] debug: ⛔️ Server wasn't able to start properly.
[develop:backend ] [2021-12-28 02:53:44.583] error: connect ECONNREFUSED 127.0.0.1:3306
[develop:backend ] Error: connect ECONNREFUSED 127.0.0.1:3306
[develop:backend ] at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
[develop:backend ] --------------------
[develop:backend ] at Protocol._enqueue (/home/xxxxx/dev/sts/backend-strapi4/backend/node_modules/mysql/lib/protocol/Protocol.js:144:48)
[develop:backend ] at Protocol.handshake (/home/xxxxx/dev/sts/backend-strapi4/backend/node_modules/mysql/lib/protocol/Protocol.js:51:23)
[develop:backend ] at Connection.connect (/home/xxxxxx/dev/sts/backend-strapi4/backend/node_modules/mysql/lib/Connection.js:116:18)
[develop:backend ] at /home/xxxxxxx/dev/sts/backend-strapi4/backend/node_modules/knex/lib/dialects/mysql/index.js:56:18
[develop:backend ] at new Promise ()
[develop:backend ] at Client_MySQL.acquireRawConnection (/home/xxxxxx/dev/sts/backend-strapi4/backend/node_modules/knex/lib/dialects/mysql/index.js:51:12)
[develop:backend ] at create (/home/xxxxx/dev/sts/backend-strapi4/backend/node_modules/knex/lib/client.js:237:39)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ERROR: "develop:backend" exited with 1.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: Command failed with exit code 1: yarn develop
at makeError (/home/xxxxx/.config/yarn/global/node_modules/execa/lib/error.js:60:11)
at handlePromise (/home/xxxx/.config/yarn/global/node_modules/execa/index.js:118:26)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async buildStarter (/home/xxxxx/.config/yarn/global/node_modules/create-strapi-starter/utils/build-starter.js:201:3)

Suggestion: Upgrade Starters & Templates to Next.js v12

It's time to upgrade Next.js from 11 to 12, the latest version!

Why?

Next.js 12 is Vercel's biggest release ever!

Rust Compiler: ~3x faster Fast Refresh and ~5x faster builds
Middleware (beta): Enabling full flexibility in Next.js with code over configuration
React 18 Support: Native Next.js APIs are now supported, as well as Suspense
Image AVIF Support: Opt-in for 20% smaller images
Bot-aware ISR Fallback: Optimized SEO for web crawlers
Native ES Modules Support: Aligning with the standardized module system
URL Imports (alpha): Import packages from any URL, no installs required
React Server Components (alpha): Try it today, including SSR streaming

To get started, here's an upgrade guide from 11 to 12.

V4 ecommerce starter fails on install

Bug report

Describe the bug

When I run the command
npx create-strapi-starter my-project next-ecommerce or yarn create strapi-starter my-project next-ecommerce

I get the following error:

This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at getPackageInfo (C:\Users\pc\AppData\Local\npm-cache\_npx\ecd569b0a81a6814\node_modules\create-strapi-starter\utils\fetch-npm-starter.js:19:27)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async getStarterInfo (C:\Users\pc\AppData\Local\npm-cache\_npx\ecd569b0a81a6814\node_modules\create-strapi-starter\utils\build-starter.js:109:26)
    at async buildStarter (C:\Users\pc\AppData\Local\npm-cache\_npx\ecd569b0a81a6814\node_modules\create-strapi-starter\utils\build-starter.js:133:7)

On a side note, the blog starter installs and runs nicely.

Steps to reproduce the behavior

try to install the ecommerce starter with npx or yarn
Coose "Quickstart" or "Custom"
See error in console

Expected behavior

The ecommerce starter installs without errors.

System

Node.js version: v16.13.0
NPM version: 8.1.0
Strapi version: v4
Database: n/a
Operating system: Windows 11

Strapi Starter Gatsby Blog Frontend won't start ; "gatsby-source-strapi" threw an error while running the sourceNodes lifecycle

Hi guys, wanted to give it a try with this starter.
Everything installed properly. Backend started without any problem.
I then created the API Token in Strapi

Then i added the Token to the .env file

But then when i start my frontend with gatsby develop it looks like he can't read the strapi nodes and I have this Error, any idea ? :
PS C:\Dev\Projects\gatsby-strapi-blog\frontend> gatsby develop
success compile gatsby files - 1.665s
success load gatsby config - 0.027s
success load plugins - 1.306s
Loaded gatsby-source-strapi-plugin
success onPreInit - 0.008s
success initialize cache - 0.330s
success copy gatsby files - 0.363s
success Compiling Gatsby Functions - 0.414s
success onPreBootstrap - 0.438s
success createSchemaCustomization - 0.013s

ERROR #11321 PLUGIN

"gatsby-source-strapi" threw an error while running the sourceNodes lifecycle:

Request failed with status code 403

Error: Request failed with status code 403

createError.js:16 createError
[frontend]/[axios]/lib/core/createError.js:16:15
settle.js:17 settle
[frontend]/[axios]/lib/core/settle.js:17:12
http.js:293 IncomingMessage.handleStreamEnd
[frontend]/[axios]/lib/adapters/http.js:293:11
readable.js:1317 endReadableNT
internal/streams/readable.js:1317:12
task_queues.js:82 processTicksAndRejections
internal/process/task_queues.js:82:21

warn The gatsby-source-strapi plugin has generated no Gatsby nodes. Do you need it?
success Checking for changed pages - 0.002s
success source and transform nodes - 0.182s
success building schema - 0.234s

ERROR #85923 GRAPHQL

There was an error in your GraphQL query:

Cannot query field "allStrapiArticle" on type "Query".

If you don't expect "allStrapiArticle" to exist on the type "Query" it is most likely a typo.
However, if you expect "allStrapiArticle" to exist there are a couple of solutions to common problems:

If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development
server
The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you
can query and what shape they have
You want to optionally use your field "allStrapiArticle" and right now it is not used anywhere. Therefore Gatsby can't infer the type and
add it to the GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned
"dummy content". Visit our docs to learn how you can define the schema for "Query":
https://www.gatsbyjs.com/docs/reference/graphql-data-layer/schema-customization#creating-type-definitions

File: gatsby-node.js:9:24

ERROR

There was an error loading your Strapi articles Cannot query field "allStrapiArticle" on type "Query".

GraphQLError: Cannot query field "allStrapiArticle" on type "Query".

graphql-runner.ts:120 GraphQLRunner.validate
[frontend]/[gatsby]/src/query/graphql-runner.ts:120:16
graphql-runner.ts:187 GraphQLRunner.query
[frontend]/[gatsby]/src/query/graphql-runner.ts:187:39
create-graphql-runner.ts:57 apply
[frontend]/[gatsby]/src/bootstrap/create-graphql-runner.ts:57:8
create-pages.ts:34 wrappedGraphQL
[frontend]/[gatsby]/src/services/create-pages.ts:34:47
gatsby-node.js:9 Object.exports.createPages
C:/Dev/Projects/gatsby-strapi-blog/frontend/gatsby-node.js:9:24
api-runner-node.js:462 runAPI
[frontend]/[gatsby]/src/utils/api-runner-node.js:462:22
api-runner-node.js:613 Promise.catch.decorateEvent.pluginName
[frontend]/[gatsby]/src/utils/api-runner-node.js:613:13
debuggability.js:384 Promise._execute
[frontend]/[bluebird]/js/release/debuggability.js:384:9
promise.js:518 Promise._resolveFromExecutor
[frontend]/[bluebird]/js/release/promise.js:518:18
promise.js:103 new Promise
[frontend]/[bluebird]/js/release/promise.js:103:10
api-runner-node.js:611
[frontend]/[gatsby]/src/utils/api-runner-node.js:611:16

failed createPages - 0.152s
success createPagesStatefully - 0.096s
info Total nodes: 36, SitePage nodes: 3 (use --verbose for breakdown)
success Checking for changed pages - 0.004s
success write out redirect data - 0.003s
success onPostBootstrap - 0.003s
info bootstrap finished - 9.589s
success onPreExtractQueries - 0.004s

ERROR #85923 GRAPHQL

There was an error in your GraphQL query:

Cannot query field "strapiGlobal" on type "Query".

If you don't expect "strapiGlobal" to exist on the type "Query" it is most likely a typo.
However, if you expect "strapiGlobal" to exist there are a couple of solutions to common problems:

If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development
server
The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you
can query and what shape they have
You want to optionally use your field "strapiGlobal" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")

File: src\components\seo.js:8:7

ERROR #85901 GRAPHQL

There was an error in your GraphQL query:

Unknown type "STRAPI_ARTICLE".

GraphQL request:2:27
1 |
2 | fragment ArticleCard on STRAPI_ARTICLE {
| ^
3 | id

File: src\pages\index.js:10:27

GraphQLError: Unknown type "STRAPI_ARTICLE".

query-compiler.js:365 processDefinitions
[frontend]/[gatsby]/src/query/query-compiler.js:365:20
query-compiler.js:176 processQueries
[frontend]/[gatsby]/src/query/query-compiler.js:176:10
query-compiler.js:78 compile
[frontend]/[gatsby]/src/query/query-compiler.js:78:19
query-watcher.ts:223 updateStateAndRunQueries
[frontend]/[gatsby]/src/query/query-watcher.ts:223:40
extract-queries.ts:18 extractQueries
[frontend]/[gatsby]/src/services/extract-queries.ts:18:3

ERROR #85923 GRAPHQL

There was an error in your GraphQL query:

Cannot query field "allStrapiArticle" on type "Query".

If you don't expect "allStrapiArticle" to exist on the type "Query" it is most likely a typo.
However, if you expect "allStrapiArticle" to exist there are a couple of solutions to common problems:

If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development
server
The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you
can query and what shape they have
You want to optionally use your field "allStrapiArticle" and right now it is not used anywhere. Therefore Gatsby can't infer the type and
add it to the GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")

File: src\pages\index.js:11:7

ERROR #85923 GRAPHQL

There was an error in your GraphQL query:

Cannot query field "strapiGlobal" on type "Query".

If you don't expect "strapiGlobal" to exist on the type "Query" it is most likely a typo.
However, if you expect "strapiGlobal" to exist there are a couple of solutions to common problems:

If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development
server
The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you
can query and what shape they have
You want to optionally use your field "strapiGlobal" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")

File: src\pages\index.js:16:7

ERROR #85901 GRAPHQL

There was an error in your GraphQL query:

Unknown type
"STRAPI__COMPONENT_SHARED_MEDIASTRAPI__COMPONENT_SHARED_QUOTESTRAPI__COMPONENT_SHARED_RICH_TEXTSTRAPI__COMPONENT_SHARED_SLIDERUnion".

GraphQL request:2:22
2 | fragment Blocks on STRAPI__COMPONENT_SHARED_MEDIASTRAPI__COMPONENT_SHARED_QUOT
| ^
| ESTRAPI__COMPONENT_SHARED_RICH_TEXTSTRAPI__COMPONENT_SHARED_SLIDERUnion {

File: src\templates\article-post.js:37:22

GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_MEDIASTRAPI__COMPONENT_SHARED_QUOTESTRAPI__COMPONENT_SHARED_RICH_TEXTSTRAPI__COMPONENT_ SHARED_SLIDERUnion".

query-compiler.js:365 processDefinitions
[frontend]/[gatsby]/src/query/query-compiler.js:365:20
query-compiler.js:176 processQueries
[frontend]/[gatsby]/src/query/query-compiler.js:176:10
query-compiler.js:78 compile
[frontend]/[gatsby]/src/query/query-compiler.js:78:19
query-watcher.ts:223 updateStateAndRunQueries
[frontend]/[gatsby]/src/query/query-watcher.ts:223:40
extract-queries.ts:18 extractQueries
[frontend]/[gatsby]/src/services/extract-queries.ts:18:3

ERROR #85901 GRAPHQL

There was an error in your GraphQL query:

Unknown type "STRAPI__COMPONENT_SHARED_RICH_TEXT".

GraphQL request:4:12
3 | __typename
4 | ... on STRAPI__COMPONENT_SHARED_RICH_TEXT {
| ^
5 | richTextBody: body {

File: src\templates\article-post.js:39:12

GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_RICH_TEXT".

query-compiler.js:365 processDefinitions
[frontend]/[gatsby]/src/query/query-compiler.js:365:20
query-compiler.js:176 processQueries
[frontend]/[gatsby]/src/query/query-compiler.js:176:10
query-compiler.js:78 compile
[frontend]/[gatsby]/src/query/query-compiler.js:78:19
query-watcher.ts:223 updateStateAndRunQueries
[frontend]/[gatsby]/src/query/query-watcher.ts:223:40
extract-queries.ts:18 extractQueries
[frontend]/[gatsby]/src/services/extract-queries.ts:18:3

ERROR #85901 GRAPHQL

There was an error in your GraphQL query:

Unknown type "STRAPI__COMPONENT_SHARED_MEDIA".

GraphQL request:15:12
14 | }
15 | ... on STRAPI__COMPONENT_SHARED_MEDIA {
| ^
16 | file {

File: src\templates\article-post.js:50:12

GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_MEDIA".

query-compiler.js:365 processDefinitions
[frontend]/[gatsby]/src/query/query-compiler.js:365:20
query-compiler.js:176 processQueries
[frontend]/[gatsby]/src/query/query-compiler.js:176:10
query-compiler.js:78 compile
[frontend]/[gatsby]/src/query/query-compiler.js:78:19
query-watcher.ts:223 updateStateAndRunQueries
[frontend]/[gatsby]/src/query/query-watcher.ts:223:40
extract-queries.ts:18 extractQueries
[frontend]/[gatsby]/src/services/extract-queries.ts:18:3

ERROR #85901 GRAPHQL

There was an error in your GraphQL query:

Unknown type "STRAPI__COMPONENT_SHARED_QUOTE".

GraphQL request:25:12
24 | }
25 | ... on STRAPI__COMPONENT_SHARED_QUOTE {
| ^
26 | title

File: src\templates\article-post.js:60:12

GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_QUOTE".

query-compiler.js:365 processDefinitions
[frontend]/[gatsby]/src/query/query-compiler.js:365:20
query-compiler.js:176 processQueries
[frontend]/[gatsby]/src/query/query-compiler.js:176:10
query-compiler.js:78 compile
[frontend]/[gatsby]/src/query/query-compiler.js:78:19
query-watcher.ts:223 updateStateAndRunQueries
[frontend]/[gatsby]/src/query/query-watcher.ts:223:40
extract-queries.ts:18 extractQueries
[frontend]/[gatsby]/src/services/extract-queries.ts:18:3

ERROR #85901 GRAPHQL

There was an error in your GraphQL query:

Unknown type "STRAPI__COMPONENT_SHARED_SLIDER".

GraphQL request:29:12
28 | }
29 | ... on STRAPI__COMPONENT_SHARED_SLIDER {
| ^
30 | files {

File: src\templates\article-post.js:64:12

GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_SLIDER".

query-compiler.js:365 processDefinitions
[frontend]/[gatsby]/src/query/query-compiler.js:365:20
query-compiler.js:176 processQueries
[frontend]/[gatsby]/src/query/query-compiler.js:176:10
query-compiler.js:78 compile
[frontend]/[gatsby]/src/query/query-compiler.js:78:19
query-watcher.ts:223 updateStateAndRunQueries
[frontend]/[gatsby]/src/query/query-watcher.ts:223:40
extract-queries.ts:18 extractQueries
[frontend]/[gatsby]/src/services/extract-queries.ts:18:3

ERROR #85923 GRAPHQL

There was an error in your GraphQL query:

Cannot query field "strapiArticle" on type "Query".

If you don't expect "strapiArticle" to exist on the type "Query" it is most likely a typo.
However, if you expect "strapiArticle" to exist there are a couple of solutions to common problems:

If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development
server
The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you
can query and what shape they have
You want to optionally use your field "strapiArticle" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add
it to the GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")

File: src\templates\article-post.js:38:5

ERROR #85901 GRAPHQL

There was an error in your GraphQL query:

Unknown type
"STRAPI__COMPONENT_SHARED_MEDIASTRAPI__COMPONENT_SHARED_QUOTESTRAPI__COMPONENT_SHARED_RICH_TEXTSTRAPI__COMPONENT_SHARED_SLIDERUnion".

GraphQL request:2:22
2 | fragment Blocks on STRAPI__COMPONENT_SHARED_MEDIASTRAPI__COMPONENT_SHARED_QUOT
| ^
| ESTRAPI__COMPONENT_SHARED_RICH_TEXTSTRAPI__COMPONENT_SHARED_SLIDERUnion {

File: src\pages\about.js:10:22

GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_MEDIASTRAPI__COMPONENT_SHARED_QUOTESTRAPI__COMPONENT_SHARED_RICH_TEXTSTRAPI__COMPONENT_ SHARED_SLIDERUnion".

query-compiler.js:365 processDefinitions
[frontend]/[gatsby]/src/query/query-compiler.js:365:20
query-compiler.js:176 processQueries
[frontend]/[gatsby]/src/query/query-compiler.js:176:10
query-compiler.js:78 compile
[frontend]/[gatsby]/src/query/query-compiler.js:78:19
query-watcher.ts:223 updateStateAndRunQueries
[frontend]/[gatsby]/src/query/query-watcher.ts:223:40
extract-queries.ts:18 extractQueries
[frontend]/[gatsby]/src/services/extract-queries.ts:18:3

ERROR #85901 GRAPHQL

There was an error in your GraphQL query:

Unknown type "STRAPI__COMPONENT_SHARED_RICH_TEXT".

GraphQL request:4:12
3 | __typename
4 | ... on STRAPI__COMPONENT_SHARED_RICH_TEXT {
| ^
5 | richTextBody: body {

File: src\pages\about.js:12:12

GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_RICH_TEXT".

query-compiler.js:365 processDefinitions
[frontend]/[gatsby]/src/query/query-compiler.js:365:20
query-compiler.js:176 processQueries
[frontend]/[gatsby]/src/query/query-compiler.js:176:10
query-compiler.js:78 compile
[frontend]/[gatsby]/src/query/query-compiler.js:78:19
query-watcher.ts:223 updateStateAndRunQueries
[frontend]/[gatsby]/src/query/query-watcher.ts:223:40
extract-queries.ts:18 extractQueries
[frontend]/[gatsby]/src/services/extract-queries.ts:18:3

ERROR #85901 GRAPHQL

There was an error in your GraphQL query:

Unknown type "STRAPI__COMPONENT_SHARED_MEDIA".

GraphQL request:15:12
14 | }
15 | ... on STRAPI__COMPONENT_SHARED_MEDIA {
| ^
16 | file {

File: src\pages\about.js:23:12

GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_MEDIA".

query-compiler.js:365 processDefinitions
[frontend]/[gatsby]/src/query/query-compiler.js:365:20
query-compiler.js:176 processQueries
[frontend]/[gatsby]/src/query/query-compiler.js:176:10
query-compiler.js:78 compile
[frontend]/[gatsby]/src/query/query-compiler.js:78:19
query-watcher.ts:223 updateStateAndRunQueries
[frontend]/[gatsby]/src/query/query-watcher.ts:223:40
extract-queries.ts:18 extractQueries
[frontend]/[gatsby]/src/services/extract-queries.ts:18:3

ERROR #85901 GRAPHQL

There was an error in your GraphQL query:

Unknown type "STRAPI__COMPONENT_SHARED_QUOTE".

GraphQL request:25:12
24 | }
25 | ... on STRAPI__COMPONENT_SHARED_QUOTE {
| ^
26 | title

File: src\pages\about.js:33:12

GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_QUOTE".

query-compiler.js:365 processDefinitions
[frontend]/[gatsby]/src/query/query-compiler.js:365:20
query-compiler.js:176 processQueries
[frontend]/[gatsby]/src/query/query-compiler.js:176:10
query-compiler.js:78 compile
[frontend]/[gatsby]/src/query/query-compiler.js:78:19
query-watcher.ts:223 updateStateAndRunQueries
[frontend]/[gatsby]/src/query/query-watcher.ts:223:40
extract-queries.ts:18 extractQueries
[frontend]/[gatsby]/src/services/extract-queries.ts:18:3

ERROR #85901 GRAPHQL

There was an error in your GraphQL query:

Unknown type "STRAPI__COMPONENT_SHARED_SLIDER".

GraphQL request:29:12
28 | }
29 | ... on STRAPI__COMPONENT_SHARED_SLIDER {
| ^
30 | files {

File: src\pages\about.js:37:12

GraphQLError: Unknown type "STRAPI__COMPONENT_SHARED_SLIDER".

query-compiler.js:365 processDefinitions
[frontend]/[gatsby]/src/query/query-compiler.js:365:20
query-compiler.js:176 processQueries
[frontend]/[gatsby]/src/query/query-compiler.js:176:10
query-compiler.js:78 compile
[frontend]/[gatsby]/src/query/query-compiler.js:78:19
query-watcher.ts:223 updateStateAndRunQueries
[frontend]/[gatsby]/src/query/query-watcher.ts:223:40
extract-queries.ts:18 extractQueries
[frontend]/[gatsby]/src/services/extract-queries.ts:18:3

ERROR #85923 GRAPHQL

There was an error in your GraphQL query:

Cannot query field "strapiAbout" on type "Query".

If you don't expect "strapiAbout" to exist on the type "Query" it is most likely a typo.
However, if you expect "strapiAbout" to exist there are a couple of solutions to common problems:

If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development
server
The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you
can query and what shape they have
You want to optionally use your field "strapiAbout" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it
to the GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")

File: src\pages\about.js:11:7

failed extract queries from components - 2.184s
success write out requires - 0.051s
success run page queries - 0.028s - 1/1 35.16/s

ERROR

Module not found: Error: Can't resolve '../../public/page-data/sq/d/4175596634.json' in
'C:\Dev\Projects\gatsby-strapi-blog\frontend\src\components'

ModuleNotFoundError: Module not found: Error: Can't resolve '../../public/page-data/sq/d/4175596634.json' in 'C:\Dev\Projects\gatsby-strapi- blog\frontend\src\components'

Compilation.js:2015
[frontend]/[webpack]/lib/Compilation.js:2015:28
NormalModuleFactory.js:798
[frontend]/[webpack]/lib/NormalModuleFactory.js:798:13
NormalModuleFactory.js:270
[frontend]/[webpack]/lib/NormalModuleFactory.js:270:22
NormalModuleFactory.js:434
[frontend]/[webpack]/lib/NormalModuleFactory.js:434:22
NormalModuleFactory.js:116
[frontend]/[webpack]/lib/NormalModuleFactory.js:116:11
NormalModuleFactory.js:670
[frontend]/[webpack]/lib/NormalModuleFactory.js:670:25
NormalModuleFactory.js:855
[frontend]/[webpack]/lib/NormalModuleFactory.js:855:8
NormalModuleFactory.js:975
[frontend]/[webpack]/lib/NormalModuleFactory.js:975:5
async.js:6883
[frontend]/[neo-async]/async.js:6883:13
NormalModuleFactory.js:950 Array.
[frontend]/[webpack]/lib/NormalModuleFactory.js:950:14
async.js:2517 arrayEachFunc
[frontend]/[neo-async]/async.js:2517:19
async.js:6858 Object.parallel
[frontend]/[neo-async]/async.js:6858:9
NormalModuleFactory.js:873 NormalModuleFactory._resolveResourceErrorHints
[frontend]/[webpack]/lib/NormalModuleFactory.js:873:12
NormalModuleFactory.js:834
[frontend]/[webpack]/lib/NormalModuleFactory.js:834:18

ERROR

Module not found: Error: Can't resolve '../../public/page-data/sq/d/3105690032.json' in
'C:\Dev\Projects\gatsby-strapi-blog\frontend\src\pages'

ModuleNotFoundError: Module not found: Error: Can't resolve '../../public/page-data/sq/d/3105690032.json' in 'C:\Dev\Projects\gatsby-strapi- blog\frontend\src\pages'

Compilation.js:2015
[frontend]/[webpack]/lib/Compilation.js:2015:28
NormalModuleFactory.js:798
[frontend]/[webpack]/lib/NormalModuleFactory.js:798:13
NormalModuleFactory.js:270
[frontend]/[webpack]/lib/NormalModuleFactory.js:270:22
NormalModuleFactory.js:434
[frontend]/[webpack]/lib/NormalModuleFactory.js:434:22
NormalModuleFactory.js:116
[frontend]/[webpack]/lib/NormalModuleFactory.js:116:11
NormalModuleFactory.js:670
[frontend]/[webpack]/lib/NormalModuleFactory.js:670:25
NormalModuleFactory.js:855
[frontend]/[webpack]/lib/NormalModuleFactory.js:855:8
NormalModuleFactory.js:975
[frontend]/[webpack]/lib/NormalModuleFactory.js:975:5
async.js:6883
[frontend]/[neo-async]/async.js:6883:13
NormalModuleFactory.js:950 Array.
[frontend]/[webpack]/lib/NormalModuleFactory.js:950:14
async.js:2517 arrayEachFunc
[frontend]/[neo-async]/async.js:2517:19
async.js:6858 Object.parallel
[frontend]/[neo-async]/async.js:6858:9
NormalModuleFactory.js:873 NormalModuleFactory._resolveResourceErrorHints
[frontend]/[webpack]/lib/NormalModuleFactory.js:873:12
NormalModuleFactory.js:834
[frontend]/[webpack]/lib/NormalModuleFactory.js:834:18

ERROR

Module not found: Error: Can't resolve '../../public/page-data/sq/d/960431041.json' in 'C:\Dev\Projects\gatsby-strapi-blog\frontend\src\pages'

ModuleNotFoundError: Module not found: Error: Can't resolve '../../public/page-data/sq/d/960431041.json' in 'C:\Dev\Projects\gatsby-strapi-b log\frontend\src\pages'

Compilation.js:2015
[frontend]/[webpack]/lib/Compilation.js:2015:28
NormalModuleFactory.js:798
[frontend]/[webpack]/lib/NormalModuleFactory.js:798:13
NormalModuleFactory.js:270
[frontend]/[webpack]/lib/NormalModuleFactory.js:270:22
NormalModuleFactory.js:434
[frontend]/[webpack]/lib/NormalModuleFactory.js:434:22
NormalModuleFactory.js:116
[frontend]/[webpack]/lib/NormalModuleFactory.js:116:11
NormalModuleFactory.js:670
[frontend]/[webpack]/lib/NormalModuleFactory.js:670:25
NormalModuleFactory.js:855
[frontend]/[webpack]/lib/NormalModuleFactory.js:855:8
NormalModuleFactory.js:975
[frontend]/[webpack]/lib/NormalModuleFactory.js:975:5
async.js:6883
[frontend]/[neo-async]/async.js:6883:13
NormalModuleFactory.js:950 Array.
[frontend]/[webpack]/lib/NormalModuleFactory.js:950:14
async.js:2517 arrayEachFunc
[frontend]/[neo-async]/async.js:2517:19
async.js:6858 Object.parallel
[frontend]/[neo-async]/async.js:6858:9
NormalModuleFactory.js:873 NormalModuleFactory._resolveResourceErrorHints
[frontend]/[webpack]/lib/NormalModuleFactory.js:873:12
NormalModuleFactory.js:834
[frontend]/[webpack]/lib/NormalModuleFactory.js:834:18

not finished Building development bundle - 2.049s

Strapi Next Corporate Starter fail to install

Hello,

I tried to install the Strapi Next Corporate Starter, but it fails to install...

I tried with Yarn and NPM, quickstart, and custom install, same problem.
I'm running on Windows 10, Node 16.15.1, NPM 8.13.2, Yarn 1.22.5

Creating a quickstart project.
Creating a new Strapi application at C:\Users\****\Documents\backend.
Creating files.
Installing @strapi/template-corporate template.
Error: ⛔️ Template installation failed: Command failed: npm install @strapi/[email protected] --no-save --silent


    at createProject (C:\Users\****\AppData\Local\Yarn\Data\global\node_modules\@strapi\generate-new\lib\create-project.js:82:15)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async createQuickStartProject (C:\Users\****\AppData\Local\Yarn\Data\global\node_modules\@strapi\generate-new\lib\create-quickstart-project.js:23:3)
error Command failed.
Exit code: 1

Thanks for your help

Relations in Database

It seems your default db implementation for relations in a custom collection is an association table. I would like to have an option to implement by foreign key directly. Is that a possibility or can you suggest a workaround? Thanks.

Strapi/Starters -n-temla🔥🔥

Missing starter for gatsby-corporate (404)

strapi-starter-gatsby-corporate mentions that it's deprecated and links to https://github.com/strapi/starters-and-templates/tree/main/packages/starters/gatsby-corporate, which doesn't exist (404).

Is someone already creating that starter, or can I help in any way?

DB Data Not Imported

When running npx create-strapi-app my-app-name --template corporate and going through the manual setup, the data to build the starter site is not imported into the DB.
The tables are created but not populated.

I've tried on several node + npm versions
node: v16.18.1
npm: 8.19.2

Blog example crashes when changing a collection types to allow i18n

Bug report

Required System information

Node.js version: v16.13.1
NPM version: 8.1.2
Strapi version: 4.4.7
Database: postgres: 10.12 (image name postgres:10.12-alpine)
Operating system: Ubuntu 22.04

Describe the bug

The blog example crashes when changing collection types to enable localization.

Steps to reproduce the behavior

Create a project with this command yarn create strapi-app api --template blog --quickstart --ts
Run the project
Go to the admin panel and click on edit in any of the collection types(could be any of them, you could do with article)
Go to advanced tab and check Enable localization for this Content-Type then save.

At this point the server will broke when restarting.

Screenshots

Code snippets

{
  "kind": "collectionType",
  "collectionName": "articles",
  "info": {
    "singularName": "article",
    "pluralName": "articles",
    "displayName": "Article",
    "description": "Create your blog content"
  },
  "options": {
    "draftAndPublish": true
  },
  "pluginOptions": {
    "i18n": {
      "localized": true
    }
  },
  "attributes": {
    "title": {
      "type": "string",
      "pluginOptions": {
        "i18n": {
          "localized": true
        }
      }
    },
    "description": {
      "type": "text",
      "maxLength": 80,
      "pluginOptions": {
        "i18n": {
          "localized": true
        }
      }
    },
    "slug": {
      "type": "uid",
      "targetField": "title"
    },
    "cover": {
      "type": "media",
      "multiple": false,
      "required": false,
      "allowedTypes": [
        "images",
        "files",
        "videos"
      ],
      "pluginOptions": {
        "i18n": {
          "localized": true
        }
      }
    },
    "author": {
      "type": "relation",
      "relation": "manyToOne",
      "target": "api::author.author",
      "inversedBy": "articles"
    },
    "category": {
      "type": "relation",
      "relation": "manyToOne",
      "target": "api::category.category",
      "inversedBy": "articles"
    },
    "blocks": {
      "type": "dynamiczone",
      "components": [
        "shared.media",
        "shared.quote",
        "shared.rich-text",
        "shared.slider"
      ],
      "pluginOptions": {
        "i18n": {
          "localized": true
        }
      }
    }
  }
}

If applicable, add code samples to help explain your problem.

Additional context

Add any other context about the problem here.

next-blog installation error

Error after yarn create strapi-starter my-project next-blog command:

Exit code: 1
Command: (node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy)
Arguments: 
Directory: /Users/a/Documents/dev/my-project/backend/node_modules/sharp
Output:
sharp: Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.13.1/libvips-8.13.1-darwin-x64.tar.br
sharp: Integrity check passed for darwin-x64
prebuild-install warn install Request timed out
gyp info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | darwin | x64
gyp info find Python using Python version 3.10.4 found at "/usr/local/bin/python3"
gyp http GET https://nodejs.org/download/release/v16.17.0/node-v16.17.0-headers.tar.gz
gyp http 200 https://nodejs.org/download/release/v16.17.0/node-v16.17.0-headers.tar.gz
gyp http GET https://nodejs.org/download/release/v16.17.0/SHASUMS256.txt
gyp http 200 https://nodejs.org/download/release/v16.17.0/SHASUMS256.txt
gyp info spawn /usr/local/bin/python3
gyp info spawn args [
gyp info spawn args   '/usr/local/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/Users/a/Documents/dev/my-project/backend/node_modules/sharp/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/usr/local/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/Users/a/Library/Caches/node-gyp/16.17.0/include/node/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/Users/a/Library/Caches/node-gyp/16.17.0',
gyp info spawn args   '-Dnode_gyp_dir=/usr/local/lib/node_modules/npm/node_modules/node-gyp',
gyp info spawn args   '-Dnode_lib_file=/Users/a/Library/Caches/node-gyp/16.17.0/<(target_arch)/node.lib',
gyp info spawn args   '-Dmodule_root_dir=/Users/a/Documents/dev/my-project/backend/node_modules/sharp',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.'
gyp info spawn args ]
gyp info spawn make
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
  CC(target) Release/obj.target/nothing/../node-addon-api/nothing.o
  LIBTOOL-STATIC Release/nothing.a
warning: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: archive library: Release/nothing.a the table of contents is empty (no object file members in the library define global symbols)
  TOUCH Release/obj.target/libvips-cpp.stamp
  CXX(target) Release/obj.target/sharp-darwin-x64/src/common.o
../src/common.cc:24:10: fatal error: 'vips/vips8' file not found
#include <vips/vips8>
         ^~~~~~~~~~~~
1 error generated.
make: *** [Release/obj.target/sharp-darwin-x64/src/common.o] Error 1
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack     at ChildProcess.emit (node:events:513:28)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
gyp ERR! System Darwin 21.5.0
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/a/Documents/dev/my-project/backend/node_modules/sharp
gyp ERR! node -v v16.17.0
gyp ERR! node-gyp -v v9.0.0
gyp ERR! not ok

 Keep trying!             

Oh, it seems that you encountered errors while installing dependencies in your project.
Don't give up, your project was created correctly.
Fix the issues mentioned in the installation errors and try to run the following command:

cd /Users/a/Documents/dev/my-project/backend && yarn install

OS: macOS Monterey 12.4
Node.JS version: 16.17.0
node-gyp version: 9.0.0

next-corporate starter: Unable to add page

Reiterating by reference this issue strapi/strapi-starter-next-corporate#76 which still exists and is current, almost one year later, in January 2023, with the latest version of next-corporate starter and Strapi v4.5.6 and the latest version of Postgres.

The backend server error thrown is:

[components_meta_metadata" ("meta_description", "meta_title", "twitter_card_type") 
values ($1, $2, $3) returning "id" -](error: insert into "components_meta_metadata" 
("meta_description", "meta_title", "twitter_card_type") values ($1, $2, $3) returning "id"
 - duplicate key value violates unique constraint "components_meta_metadata_pkey")

Node version is too high??

On install using yarn create strapi-starter my-project next-blog I get the following failure:

Error while installing dependencies:
warning ../../../package.json: No license field
error [email protected]: The engine "node" is incompatible with this module. Expected version ">=12.x.x <=16.x.x". Got "18.5.0"
error Found incompatible module.

 Keep trying!             

Oh, it seems that you encountered errors while installing dependencies in your project.
Don't give up, your project was created correctly.
Fix the issues mentioned in the installation errors and try to run the following command:

cd /Users/jordanlambrecht/dev-local/my-project/backend && yarn install

Next Blog : Cannot Start after installation

Starting: develop:frontend
[develop:frontend] node:internal/modules/cjs/loader:959
[develop:frontend] throw err;
[develop:frontend] ^
[develop:frontend]
[develop:frontend] Error: Cannot find module 'D:\www\strapi_cms\my-project\develop:frontend'
[develop:frontend] at Function.Module._resolveFilename (node:internal/modules/cjs/loader:956:15)
[develop:frontend] at Function.Module._load (node:internal/modules/cjs/loader:804:27)
[develop:frontend] at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
[develop:frontend] at node:internal/main/run_main_module:17:47 {
[develop:frontend] code: 'MODULE_NOT_FOUND',
[develop:frontend] requireStack: []

[develop:backend ] Starting: develop:backend
[develop:backend ] node:internal/modules/cjs/loader:959
[develop:backend ] throw err;
[develop:backend ] ^
[develop:backend ]
[develop:backend ] Error: Cannot find module 'D:\www\strapi_cms\my-project\develop:backend'
[develop:backend ] at Function.Module._resolveFilename (node:internal/modules/cjs/loader:956:15)
[develop:backend ] at Function.Module._load (node:internal/modules/cjs/loader:804:27)
[develop:backend ] at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
[develop:backend ] at node:internal/main/run_main_module:17:47 {
[develop:backend ] code: 'MODULE_NOT_FOUND',
[develop:backend ] requireStack: []
[develop:backend ] }

Nodejs Version : 16.17
OS : Windows 11

v4 Strapi - next-corportate template sql error

When I try to install the corporate demo template

  npx create-strapi-app demoapp --template corporate --quickstart

I get this error

 Project information                                                          

┌────────────────────┬──────────────────────────────────────────────────┐
│ Time               │ Fri May 20 2022 12:17:46 GMT-0400 (Eastern Dayl… │
│ Launched in        │ 3109 ms                                          │
│ Environment        │ development                                      │
│ Process PID        │ 12248                                            │
│ Version            │ 4.1.11 (node v14.19.1)                           │
│ Edition            │ Community                                        │
└────────────────────┴──────────────────────────────────────────────────┘

 Actions available                                                            

One more thing...
Create your first administrator 💻 by going to the administration panel at:

┌─────────────────────────────┐
│ http://localhost:1337/admin │
└─────────────────────────────┘

[2022-05-20 12:17:46.990] http: GET /admin (27 ms) 200
[2022-05-20 12:17:47.176] http: GET /admin/project-type (107 ms) 200
[2022-05-20 12:17:47.321] http: GET /admin/init (67 ms) 200
SqliteError: insert into `globals_localizations_links` (`global_id`, `inv_global_id`) values (2, 1) - FOREIGN KEY constraint failed
    at Client_BetterSQLite3._query (/Users/paulbratslavsky/Desktop/test/demoapp/node_modules/knex/lib/dialects/better-sqlite3/index.js:39:38)
    at executeQuery (/Users/paulbratslavsky/Desktop/test/demoapp/node_modules/knex/lib/execution/internal/query-executioner.js:37:17)
    at Client_BetterSQLite3.query (/Users/paulbratslavsky/Desktop/test/demoapp/node_modules/knex/lib/client.js:146:12)
    at Runner.query (/Users/paulbratslavsky/Desktop/test/demoapp/node_modules/knex/lib/execution/runner.js:130:36)
    at ensureConnectionCallback (/Users/paulbratslavsky/Desktop/test/demoapp/node_modules/knex/lib/execution/internal/ensure-connection-callback.js:13:17)
    at Runner.ensureConnection (/Users/paulbratslavsky/Desktop/test/demoapp/node_modules/knex/lib/execution/runner.js:307:20)
    at async Runner.run (/Users/paulbratslavsky/Desktop/test/demoapp/node_modules/knex/lib/execution/runner.js:30:19)
    at async Object.execute (/Users/paulbratslavsky/Desktop/test/demoapp/node_modules/@strapi/database/lib/query/query-builder.js:354:22)
    at async Object.attachRelations (/Users/paulbratslavsky/Desktop/test/demoapp/node_modules/@strapi/database/lib/entity-manager.js:496:11)
    at async Object.create (/Users/paulbratslavsky/Desktop/test/demoapp/node_modules/@strapi/database/lib/entity-manager.js:175:7)
    at async Object.create (/Users/paulbratslavsky/Desktop/test/demoapp/node_modules/@strapi/strapi/lib/services/entity-service/index.js:172:18)
    at async Object.<anonymous> (/Users/paulbratslavsky/Desktop/test/demoapp/node_modules/@strapi/strapi/lib/services/entity-service/index.js:67:20)
    at async Object.create (/Users/paulbratslavsky/Desktop/test/demoapp/node_modules/@strapi/plugin-i18n/server/services/entity-service-decorator.js:118:19)
    at async createEntry (/Users/paulbratslavsky/Desktop/test/demoapp/src/bootstrap.js:93:26)
    at async /Users/paulbratslavsky/Desktop/test/demoapp/src/bootstrap.js:189:5
SqliteError: insert into `pages_localizations_links` (`inv_page_id`, `page_id`) values (1, 5) - FOREIGN KEY constraint failed
    at Client_BetterSQLite3._query (/Users/paulbratslavsky/Desktop/test/demoapp/node_modules/knex/lib/dialects/better-sqlite3/index.js:39:38)
    at executeQuery (/Users/paulbratslavsky/Desktop/test/demoapp/node_modules/knex/lib/execution/internal/query-executioner.js:37:17)
    at Client_BetterSQLite3.query (/Users/paulbratslavsky/Desktop/test/demoapp/node_modules/knex/lib/client.js:146:12)
    at Runner.query (/Users/paulbratslavsky/Desktop/test/demoapp/node_modules/knex/lib/execution/runner.js:130:36)
    at ensureConnectionCallback (/Users/paulbratslavsky/Desktop/test/demoapp/node_modules/knex/lib/execution/internal/ensure-connection-callback.js:13:17)
    at Runner.ensureConnection (/Users/paulbratslavsky/Desktop/test/demoapp/node_modules/knex/lib/execution/runner.js:307:20)
    at async Runner.run (/Users/paulbratslavsky/Desktop/test/demoapp/node_modules/knex/lib/execution/runner.js:30:19)
    at async Object.execute (/Users/paulbratslavsky/Desktop/test/demoapp/node_modules/@strapi/database/lib/query/query-builder.js:354:22)
    at async Object.attachRelations (/Users/paulbratslavsky/Desktop/test/demoapp/node_modules/@strapi/database/lib/entity-manager.js:496:11)
    at async Object.create (/Users/paulbratslavsky/Desktop/test/demoapp/node_modules/@strapi/database/lib/entity-manager.js:175:7)
    at async Object.create (/Users/paulbratslavsky/Desktop/test/demoapp/node_modules/@strapi/strapi/lib/services/entity-service/index.js:172:18)
    at async Object.<anonymous> (/Users/paulbratslavsky/Desktop/test/demoapp/node_modules/@strapi/strapi/lib/services/entity-service/index.js:67:20)
    at async Object.create (/Users/paulbratslavsky/Desktop/test/demoapp/node_modules/@strapi/plugin-i18n/server/services/entity-service-decorator.js:118:19)
    at async createEntry (/Users/paulbratslavsky/Desktop/test/demoapp/src/bootstrap.js:93:26)
    at async /Users/paulbratslavsky/Desktop/test/demoapp/src/bootstrap.js:174:5

Had some feedback from Derrick

He hinted that those "errors are usually because a seed process is trying to insert one set of data before the other required one exists"

next-blog installation failed at /frontend - unable to resolve dependency tree

The installation using npx create-strapi-starter my-site next-blog fails at the /frontend. I get the following dependency error:

Installing frontend dependencies
⠴ Installing dependencies:This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: Command failed with exit code 1: npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"17.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^17.0.2" from [email protected]
npm ERR! node_modules/next
npm ERR!   next@"^11.0.0" from the root project
npm ERR!   peer next@">=10.2.0" from [email protected]
npm ERR!   node_modules/eslint-config-next
npm ERR!     dev eslint-config-next@"^11.0.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!

Would be great to see this starter use the latest version of NextJs (v13), or at least a version closer to it—v11 is pretty out of date.

Node: v16.14.0
npm: v8.3.1

next-corporate starter: Lead submission doesn't work (+ workaround)

Rant

Yet another easy-to-fix (?) bug in the corporate-starter template that has existed for months. Illustrates the complete abandonment of this repo, with open issues, as of this writing, dating back to December 2021. No triage, no assignment, just slow decay. Strapi, this is your street sign, your advertising banner, your welcome committee, your business card, your entry hall, the funnel to get new developers excited about Strapi, and mostly nothing works. Of the $31 MM venture funding, wouldn't it make sense to clip off $100K for a person to keep these simple starters and templates maintained? Or at least triage these issues here so developers feel like you're taking this seriously? Hard to spread the gospel about Strapi when the basic starter packages simply do not work.

Issue

After installing the next-corporate starter, which also doesn't work out of the box with version 4.5.x (see #67 ), email POST submissions to http://localhost:1337/api/lead-form-submissions fail with an error visible in the GUI as An error occured please try again.

Cause

Apparently the API now expects the body of the POST payload to be wrapped in to a data object, but the starter was never adapted to that, and apparently nobody ever tested it recently.

Apparently the frontend sends the following JSON payload to the API:

{"email": "[email protected]", "location": "Home Page Bottom"}

Which is not in line with what the API expects; it expects the payload to be wrapped into a data object like so:

{"data": {
    "email": "[email protected]", "location": "Home Page Bottom"
}}

Workaround

As a hacky quick-fix workaround, I inserted the following three lines into ./frontent/utils/api.js:

// Merge default and user options
const mergedOptions = {
	headers: {
		"Content-Type": "application/json",
	},
	...options,
}
// @HACK begins here
if (mergedOptions.body && typeof mergedOptions.body === "string") {
	mergedOptions.body = `{\"data\": ${mergedOptions.body}}`
}
// @HACK ends here
// Build request URL
const queryString = qs.stringify(urlParamsObject)

I have no idea what the larger implications of this hack are and if it api.js will work as expected under all circumstances after this modification. But it got the email submission to work.

Create New Custom Page but no data

Please let me know. how to fix it.

I need to new page for Register Form.

Error : TypeError: Cannot read properties of undefined (reading 'submitCampaign')

url : localhost:3000/campaign

Font-end
`import { useState } from "react";
import { fetchAPI } from "utils/api";
import * as yup from "yup";
import { Formik, Form, Field} from "formik";
import Button from "../elements/button";

const Campaign = ({ data }) => {
const [loading, setLoading] = useState(false);
const CampaignSchema = yup.object().shape({

})

return (

<Formik
  initialValues={{ email: "" }}
  validationSchema={CampaignSchema}
  onSubmit={async (values, { setSubmitting, setErrors }) => {
    setLoading(true);
   
  }}
>
  {({ errors, touched, isSubmitting, data }) => (
    <div>
      <Form className="flex flex-col md:flex-row gap-4">

      <label htmlFor="preName">Pre Name</label> 
        <Field as="select" name="prename">
          <option value="Mr">Mr</option>
          <option value="Miss">Miss</option>
          <option value="Ms">Ms</option>              
        </Field>

      <label htmlFor="firstName">First Name</label>
        <Field
          className="text-base focus:outline-none py-4 md:py-0 px-4 border-2 rounded-md"              
          name="firstname"
        /> 

        <label htmlFor="lastName">Last Name</label>
        <Field
          className="text-base focus:outline-none py-4 md:py-0 px-4 border-2 rounded-md"              
          name="lastname"           
        />        

        <Button
          type="submit"
          button={data.submitCampaign}
          disabled={isSubmitting}
          loading={loading}
        />
        
      </Form>
      <p className="text-red-500 h-12 text-sm mt-1 ml-2 text-left">
        {(errors.email && touched.email && errors.email) || errors.api}
      </p>
    </div>
  )}
</Formik>

);
};

export default Campaign;
`
setting in section.js

Back-end (Strapi)

Frontend setup fail

After command used:
npx create-strapi-starter mysite3 next-corporate

Backend installed and run successfully but frontend did not.
I'm getting this error:
TypeError: Cannot destructure property 'metadata' of 'global.attributes' as it is undefined.

node : 16.15.0 (I also tried Node version 14.21.0)
npm : 8.5.5

Anyone can help me with this issue?
regards,

strapi / starters-and-templates Goto Github PK

starters-and-templates's Introduction

Open-source headless CMS, self-hosted or Cloud you’re in control.

Getting Started

⏳ Installation

🖐 Requirements

Features

Contributing

Community support

Migration

Roadmap

Documentation

Try live demo

License

starters-and-templates's People

Contributors

Stargazers

Watchers

Forkers

starters-and-templates's Issues

Steps to reproduce:

Errors

Steps to reproduce

Version

Buggy code:

Fixed code:

Bug report

Describe the bug

Steps to reproduce the behavior

Expected behavior

System

Short summary

Steps to reproduce

Description

Steps to reproduce + outputs

Bug report

Describe the bug

Steps to reproduce the behavior

Expected behavior

System

Bug report

Required System information

Describe the bug

Steps to reproduce the behavior

Screenshots

Code snippets

Additional context

Rant

Issue

Cause

Workaround

Recommend Projects

Recommend Topics

Recommend Org