对于想了解Gatsby+Reach路由器：控制客户端路由路径的最佳模式的读者，本文将是一篇不可错过的文章，我们将详细介绍路由控制工具，并且为您提供关于'gatsby-source-graphql'导致

对于想了解Gatsby + Reach 路由器：控制客户端路由路径的最佳模式的读者，本文将是一篇不可错过的文章，我们将详细介绍路由控制工具，并且为您提供关于'gatsby-source-graphql' 导致加载插件错误引用 'gatsby/graphql' 我将它包含在我的 gatsby-config.js 中，如下所示：但它产生了这个错误：我尝试过的：我使用 gatsby info --clipboard 的环境报告是：有什么想法吗？导致问题的原因如下：、Gatsby (gatsby-source-strapi) - 您的数据问题中存在冲突的字段类型、Gatsby - webpack 无法使用 `gatsby-plugin-alias-imports`、Gatsby Develop 工作正常，Gatsby Build 导致 WebpackError: Minified React error #130的有价值信息。

• Gatsby + Reach 路由器：控制客户端路由路径的最佳模式（路由控制工具）
• 'gatsby-source-graphql' 导致加载插件错误引用 'gatsby/graphql' 我将它包含在我的 gatsby-config.js 中，如下所示：但它产生了这个错误：我尝试过的：我使用 gatsby info --clipboard 的环境报告是：有什么想法吗？导致问题的原因如下：
• Gatsby (gatsby-source-strapi) - 您的数据问题中存在冲突的字段类型
• Gatsby - webpack 无法使用 `gatsby-plugin-alias-imports`
• Gatsby Develop 工作正常，Gatsby Build 导致 WebpackError: Minified React error #130

Gatsby + Reach 路由器：控制客户端路由路径的最佳模式（路由控制工具）

如何解决Gatsby + Reach 路由器：控制客户端路由路径的最佳模式

我的目标是在使用 Gatsby (v2) 和 @reach/router 时以最佳模式启用以下类型的静态和动态路径。我遇到的问题是 Gatsby 文档将您设置为在每个动态路由上添加路径 /app 的前缀，这不适合我的用例。

所需路径：

• /：静态路由和构建时生成
• /about：静态路由和构建时生成
• /:username：动态路由和运行时生成
• /:username/:postTitleSlug：动态路由和运行时生成

按照 Gatsby 文档，我有这个文件夹结构：

/pages
  index.jsx
  about.jsx
  app.jsx
/templates
  profile.jsx // for the /:username path
  post.jsx // for the /:username/:postTitleSlug path

app.jsx

const Routes = () => (
  <Router>
    <Profile path="/:username" />
    <Read path="/:username/:slug" />
  </Router>
);

gatsby-node.js

exports.onCreatePage = async ({ page,actions }) => {
  const { createPage } = actions;

  if (page.path.match(/^\\/app/)) {
    await createPage({
      path: ''app'',matchPath: ''/app/*'',component: path.resolve(''src/templates/Profile/index.js''),});
  }
};

是否可以取消“应用”命名法并在基本路径 / 之外键入一些动态路由？

FWIW，我的第一个尝试修复是使 pages/index.jsx 只是一个路由器，类似于 this post。这似乎是一个潜在的解决方案，但我不清楚 gatsby-node.js 所需的更新。

'gatsby-source-graphql' 导致加载插件错误引用 'gatsby/graphql' 我将它包含在我的 gatsby-config.js 中，如下所示：但它产生了这个错误：我尝试过的：我使用 gatsby info --clipboard 的环境报告是：有什么想法吗？导致问题的原因如下：

如何解决''gatsby-source-graphql'' 导致加载插件错误引用 ''gatsby/graphql'' 我将它包含在我的 gatsby-config.js 中，如下所示：但它产生了这个错误：我尝试过的：我使用 gatsby info --clipboard 的环境报告是：有什么想法吗？导致问题的原因如下：

我已经添加了一个可用的 Gatsby 安装，但是，在尝试构建一些 graphQL 构建时数据获取时，我遇到了一个问题，该问题导致错误运行 npm start (gatsby develop) 或 gatsby build。

我按照此处的说明安装了 gatsby-source-graphql： https://www.npmjs.com/package/gatsby-source-graphql

我将它包含在我的 gatsby-config.js 中，如下所示：

module.exports = {
  // Optional
  siteMetadata: {
    title: `Title from siteMetadata`,},plugins: [
    {
      resolve: `gatsby-plugin-manifest`,options: {
        name: "Project Template",short_name: "PT",start_url: "/",background_color: "#6b37bf",theme_color: "#6b37bf",// Enables "Add to Homescreen" prompt and disables browser UI (including back button)
        // see https://developers.google.com/web/fundamentals/web-app-manifest/#display
        display: "standalone",icon: "src/images/icon.png",// This path is relative to the root of the site.
        // An optional attribute which provides support for CORS check.
        // If you do not provide a crossOrigin option,it will skip CORS for manifest.
        // Any invalid keyword or empty string defaults to `anonymous`
        crossOrigin: `use-credentials`,{
      resolve: `gatsby-source-filesystem`,options: {
        name: `images`,path: `${__dirname}/src/images`,// GraphQL APIs for use during build-time.
    // https://www.npmjs.com/package/gatsby-source-graphql
    //////////////////////////////////////////////////////
    {
      resolve: "gatsby-source-graphql",options: {
        // Arbitrary name for the remote schema Query type
        typeName: "SpaceX",// Field under which the remote schema will be accessible. You''ll use this in your Gatsby query
        fieldName: "spaceX",// Url to query from
        url: "https://api.spacex.land/graphql/",// {
    //   resolve: "gatsby-source-graphql",//   options: {
    //     // Arbitrary name for the remote schema Query type
    //     typeName: "SWAPI",//     // Field under which the remote schema will be accessible. You''ll use this in your Gatsby query
    //     fieldName: "swapi",//     // Url to query from
    //     url: "https://swapi-graphql.netlify.app/.netlify/functions/index",//   },// },`gatsby-transformer-sharp`,`gatsby-plugin-sharp`,`gatsby-plugin-react-helmet`,`gatsby-theme-material-ui`,{
      resolve: `gatsby-plugin-nprogress`,options: {
        // Setting a color is optional.
        color: `tomato`,// disable the loading spinner.
        showSpinner: false,`gatsby-plugin-transition-link`,`gatsby-plugin-layout`,// Trial and error showed this needs to be last (But that doesn''t mean it will always work in the dev environment,try npm run clean or if that fails - test in build)
  ],}

但它产生了这个错误：

Error in "/Users//Documents/projects/project/node_modules/gatsby-source-graphql/gatsby-node.js":
Cannot find module ''gatsby/graphql''
  Error: Cannot find module ''gatsby/graphql''
  - loader.js:636 Function.Module._resolveFilename
    internal/modules/cjs/loader.js:636:15
  - loader.js:562 Function.Module._load
    internal/modules/cjs/loader.js:562:25
  - loader.js:692 Module.require
    internal/modules/cjs/loader.js:692:17
  - v8-compile-cache.js:159 require
    [client]/[v8-compile-cache]/v8-compile-cache.js:159:20
  - gatsby-node.js:8 Object.<anonymous>
    [tbwa-project-template]/[gatsby-source-graphql]/gatsby-node.js:8:5
  - v8-compile-cache.js:178 Module._compile
    [client]/[v8-compile-cache]/v8-compile-cache.js:178:30
  - loader.js:789 Object.Module._extensions..js
    internal/modules/cjs/loader.js:789:10
  - loader.js:653 Module.load
    internal/modules/cjs/loader.js:653:32
  - loader.js:593 tryModuleLoad
    internal/modules/cjs/loader.js:593:12
  - loader.js:585 Function.Module._load
    internal/modules/cjs/loader.js:585:3
  - loader.js:692 Module.require
    internal/modules/cjs/loader.js:692:17
  - v8-compile-cache.js:159 require
    [client]/[v8-compile-cache]/v8-compile-cache.js:159:20
  - resolve-module-exports.ts:197 resolveModuleExports
    [client]/[gatsby]/src/bootstrap/resolve-module-exports.ts:197:26
  - validate.ts:348 forEach
    [client]/[gatsby]/src/bootstrap/load-plugins/validate.ts:348:31
  - Array.forEach
  - validate.ts:340 collatePluginAPIs
    [client]/[gatsby]/src/bootstrap/load-plugins/validate.ts:340:20
not finished load plugins - 0.727s
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! project-template@1.0.0 start: `gatsby develop`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the project-template@1.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/_logs/2021-02-04T00_31_34_070Z-debug.log

我尝试过的：

• 我在配置中尝试了两种不同的 gatsby-source-graphql 定义（一次只有一种），但都产生了错误。第二个（上面已注释掉）直接取自 The github page example 和 Gatsby example。

• 我已经尝试更改插件的顺序（我已经尝试了所有位置），但仍然出现错误。

• 如果我在配置中评论任何和所有 gatsby-source-graphql 部分，它不会产生错误。

• 如果我注释掉所有插件除了 gatsby-source-graphql 部分之一，我仍然得到完全相同的错误。

• 我也试过删除 node_modules 文件夹，运行 npm run clean，然后再次 npm install 没有任何变化。

• 我也尝试了以下链接中描述的 DanceParty 解决方案，没有任何变化： https://github.com/gatsbyjs/gatsby/issues/8249

• 我试过运行 npm update 和 npm install npm@latest -g，但没有看到任何变化。

我使用 gatsby info --clipboard 的环境报告是：

  System:
    OS: macOS 10.15.7
    cpu: (4) x64 Intel(R) Core(TM) i5-6287U cpu @ 3.10GHz
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 10.23.1 - /usr/local/bin/node
    npm: 6.14.10 - /usr/local/bin/npm
  Languages:
    Python: 2.7.16 - /usr/bin/python
  browsers:
    Chrome: 88.0.4324.96
    Firefox: 85.0
    Safari: 14.0.2
  npmPackages:
    gatsby: ^2.26.1 => 2.32.0
    gatsby-image: ^2.10.0 => 2.11.0
    gatsby-plugin-layout: ^1.9.0 => 1.10.0
    gatsby-plugin-manifest: ^2.11.0 => 2.12.0
    gatsby-plugin-material-ui: ^2.1.10 => 2.1.10
    gatsby-plugin-nprogress: ^2.9.0 => 2.10.0
    gatsby-plugin-react-helmet: ^3.8.0 => 3.10.0
    gatsby-plugin-sharp: ^2.13.0 => 2.14.0
    gatsby-plugin-transition-link: ^1.20.5 => 1.20.5
    gatsby-source-filesystem: ^2.10.0 => 2.11.0
    gatsby-theme-material-ui: ^1.0.13 => 1.0.13
    gatsby-transformer-sharp: ^2.11.0 => 2.12.0
  npmGlobalPackages:
    gatsby-cli: 2.19.0

有什么想法吗？

解决方法

Gatsby (gatsby-source-strapi) - 您的数据问题中存在冲突的字段类型

exports.createSchemaCustomization = ({ actions }) => {
    const { createTypes } = actions
    const typeDefs = `
      type StrapiLandingPages implements Node {
        programmes: [StrapiLandingPagesProgrammes]
      }
      type StrapiLandingPagesProgrammes {
        certification: StrapiLandingPagesProgrammesCertification
      }
      type StrapiLandingPagesProgrammesCertification implements Node @dontInfer {
        id: Int!
        Title: String
        slugUid: String
        sectionTitle: String
        content: String
        published_at: Date @dateformat
        created_at: Date @dateformat
        updated_at: Date @dateformat
      }
    `
    createTypes(typeDefs)
}

import Nav from "../components/Nav"
import Intro from "../components/Intro"
import About from "../components/About"
import Experience from "../components/Experience"
import Projects from "../components/Projects"
import Contact from "../components/Contact"
import Footer from "../components/Footer"

const path = require(''path'')
module.exports = {
  siteMetadata: {
    title: "Site Title",},plugins: [
    {
      resolve: "gatsby-plugin-alias-imports",options: {
        alias: {
          ''@components'': path.resolve(__dirname,''src/components''),''@pages'': path.resolve(__dirname,''src/pages''),extensions: [
          "js",],}
    },...
    ...

.
├── README.md
├── gatsby-config.js
├── package.json
├── src
│   ├── components
│   │   ├── about.js
│   │   ├── contact.js
│   │   ├── experience.js
│   │   ├── footer.js
│   │   ├── intro.js
│   │   ├── nav.js
│   │   └── projects.js
│   ├── pages
│   │   ├── 404.js
│   │   └── index.js
│   └── scss
│       └── main.scss
├── static
│   └── static
│       └── icons
│           ├── github.svg
│           ├── instagram.svg
│           └── linkedin-in.svg
└── yarn.lock

import { Nav,Intro,About,Experience,Projects,Contact,Footer } from "@components"

 ERROR #98124  WEBPACK
Generating development SSR bundle Failed
Can''t resolve ''@components'' in ''/Users/James/Projects/personal-site/src/pages''
If you''re trying to use a package make sure that ''@components'' is installed. If you''re trying to use a
local file make sure that the path is correct.
File: src/pages/index.js:2:0

export { default as Nav } from ''./nav'';
export { default as Footer } from ''./footer'';
export { default as About } from ''./about'';
export { default as Contact } from ''./contact'';
export { default as Experience } from ''./experience'';
export { default as Intro } from ''./intro'';
export { default as Projects } from ''./projects'';

success rewriting compilation hashes - 0.014s
success Writing page-data.json files to public directory - 0.002s - 0/0 0.00/s
success Building HTML renderer - 2.063s

 ERROR 

Page data from page-data.json for the Failed page "/photos/": {
  "componentChunkName": "component---src-pages-photos-js","path": "/photos/","result": {
    "pageContext": {}
  },"staticQueryHashes": []
}

Failed Building static HTML for pages - 0.277s

 ERROR #95313 

Building static HTML Failed for path "/photos/"

See our docs page for more info on this error: https://gatsby.dev/debug-html





  Webpackerror: Minified React error #130; visit https://reactjs.org/docs/error-decoder.html?invariant=130&args[]=object&args[]= for the full message or use the non-minified dev environment for full errors and add  itional helpful warnings.

  - static-entry.js:286 
    webpack:/the-last-batten/.cache/static-entry.js:286:22


not finished Caching JavaScript and CSS webpack compilation - 2.571s
not finished Caching HTML renderer compilation - 0.305s

The full text of the error you just encountered is:

Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object.

export const photos = [
  {
    src: "https://source.unsplash.com/2ShvY8Lf6l0/800x599",width: 4,height: 3
  },{
    src: "https://source.unsplash.com/Dm-qxdynoEc/800x799",width: 1,height: 1
  },{
    src: "https://source.unsplash.com/qDkso9nvCg0/600x799",width: 3,height: 4
  },{
    src: "https://source.unsplash.com/iecJiKe_RNg/600x799",{
    src: "https://source.unsplash.com/epcsn8Ed8kY/600x799",{
    src: "https://source.unsplash.com/NQSWvyVRIJk/800x599",{
    src: "https://source.unsplash.com/zh7GEuORbUw/600x799",{
    src: "https://source.unsplash.com/PpOHJezOalU/800x599",{
    src: "https://source.unsplash.com/I1ASdgphUH4/800x599",{
    src: "https://source.unsplash.com/XiDA78wAZVw/600x799",{
    src: "https://source.unsplash.com/x8xJpClTvR0/800x599",{
    src: "https://source.unsplash.com/qGQNmBE7mYw/800x599",{
    src: "https://source.unsplash.com/NuO6iTBkHxE/800x599",{
    src: "https://source.unsplash.com/pF1ug8ysTtY/600x400",{
    src: "https://source.unsplash.com/A-fubu9QJxE/800x533",{
    src: "https://source.unsplash.com/5P91SF0zNsI/740x494",height: 3
  }
];