Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't run gatsby build #164

Open
pannoury opened this issue Jun 9, 2022 · 2 comments
Open

Can't run gatsby build #164

pannoury opened this issue Jun 9, 2022 · 2 comments

Comments

@pannoury
Copy link

pannoury commented Jun 9, 2022

ERROR

Page data from page-data.json for the failed page "/en/": {
"componentChunkName": "component---src-pages-index-js",
"path": "/en/",
"result": {
"pageContext": {
"locale": "en",
"hrefLang": "en-US",
"originalPath": "/",
"dateFormat": "DD/MM/YYYY"
}
},
"staticQueryHashes": [
"1239077767",
"3280999885"
]
}

failed Building static HTML for pages - 3.482s

ERROR #95313

Building static HTML failed for path "/en/"

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

10 |
11 |

12 | const [, base] = path.split(/)
| ^
13 |
14 | // If for whatever reason we receive an already localized path
15 | // (e.g. if the path was made with location.pathname)

WebpackError: TypeError: Cannot read properties of undefined (reading 'split')

  • helpers.js:12
    [gatsby-starter-minimal]/[gatsby-theme-i18n]/src/helpers.js:12:25

  • localized-link.js:13
    [gatsby-starter-minimal]/[gatsby-theme-i18n]/src/components/localized-link.js:13:24

  • abort.js:13
    [gatsby-starter-minimal]/[asynckit]/lib/abort.js:13:1

  • extends.js:15
    [gatsby-starter-minimal]/[@babel]/runtime/helpers/extends.js:15:1

  • abort.js:22
    [gatsby-starter-minimal]/[asynckit]/lib/abort.js:22:1

  • abort.js:21
    [gatsby-starter-minimal]/[asynckit]/lib/abort.js:21:27

  • inheritsLoose.js:7
    [gatsby-starter-minimal]/[@babel]/runtime/helpers/inheritsLoose.js:7:1

  • static-entry.js:295
    gatsby-starter-minimal/.cache/static-entry.js:295:22

@Assitan
Copy link

Assitan commented Jan 8, 2023

Did you find a solution? I have the same error ...

@pannoury
Copy link
Author

Sadly not. I have switched entirety to next.js since I faced this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants