Replies: 3 comments 1 reply
-
This looks like a bug - can you open a bug report ( https://github.com/gatsbyjs/gatsby/issues/new?assignees=&labels=type%3A+bug&template=BUG_REPORT.yml ) ideally with reproduction? |
Beta Was this translation helpful? Give feedback.
-
The problem with me was also in .babelrc for "@babel/preset-env", the setting |
Beta Was this translation helpful? Give feedback.
-
Thanks for the babel hint, I am facing the same issue in NRWL NX monorepo having gatsby projects. {
"presets": [
[
"@nrwl/gatsby/babel",
{
"reactRuntime": "automatic"
}
],
[
"@babel/preset-env",
{
"loose": false // needed for Gatsby HEAD API
}
]
],
"plugins": [
["@babel/plugin-proposal-class-properties", { "loose": true }], // disables warning
["@babel/plugin-proposal-private-methods", { "loose": true }], // disables warning
["@babel/plugin-proposal-private-property-in-object", { "loose": true }] // disables warning
]
} But the better approach would be to improve the implementation on Gatsby's Heads API side, right? Can you please improve it try/catch or ignore such cases like described by @BArtistically ? |
Beta Was this translation helpful? Give feedback.
-
Why am I getting this issue? I am getting this issue while I try to route
`
One unhandled runtime error found in your files. See the list below to fix it:
Error in function eval in ./.cache/head/head-export-handler-for-browser.js:18
e.remove is not a function
./.cache/head/head-export-handler-for-browser.js:18
Open in Editor
16 | const removePrevHeadElements = () => {
17 | const prevHeadNodes = [...document.querySelectorAll(
[data-gatsby-head]
)]Beta Was this translation helpful? Give feedback.
All reactions