-
Notifications
You must be signed in to change notification settings - Fork 54
WebpackError: Cannot read property 'node' of undefined #10
Comments
Unfortunately, that error message is miss-leading, this is the actual error.
Check the Author filename example for 'casper' user: Expected formatting for an author JSON file:
|
Adding build time error to warn users if ‘authors’ folder is missing and improving posts and authors content documentation. Resolves #10
Adding build time error to warn users if ‘authors’ folder is missing and improving posts and authors content documentation. Resolves #10
@antonioOrtiz Feel free to re-open this issue if you are still running into trouble. |
Hi @haysclark after adding nodes in pageContex property in tag.jsx issue is fixed now. Like this But still there is the |
* fix: re-adding Disqus support enable Disqus comments in posts by providing a ‘disqusShortname’ in the SiteConfig.js. Resolved haysclark#9 * chore(release): 1.0.4 * fix: adding basic validation for authors Adding build time error to warn users if ‘authors’ folder is missing and improving posts and authors content documentation. Resolves haysclark#10 * fix: fixing sample-post dates and folder names Posts now to have YEAR-MONTH-DAY formatting, allowing GraphQL to sort them correctly. Post folder names corrected to match the date in each .md file. * perf: removing dead GraphQL query * chore(release): 1.0.5 * fix: improving npm ‘clean’ script to wipe .cache Sometime Gatsby does not clear the .cache folder which can lead to confusion. Running ‘npm clean’, will now delete both public and .cache to aid in resolving this issue. * fix: fixing MainNav rendering Adding missing ‘overlay’ and ‘clearfix’ CSS classes to MainNav to resolve render issue when no Cover image is provided. Updating Big-Sample-Post to have no cover for validation Resolves haysclark#18 * chore(release): 1.0.6 * fix: adding yarn.lock to fix install issues Users installing the project with Yarn were missing a critical child dependancies for prismjs@1.9.0. Resolves haysclark#21 * chore(release): 1.0.7 * chore: updating README with more specific install steps * added import for prismjs css file to fix missing syntax highlighting * fix: Adding local image for post cover example Resolves haysclark#17 * chore: updating package-lock.json * fix: ignoring linting error - due to Prisma being added for Gatsby 2.0 support, we are ignoring this minor issue * chore(release): 1.0.8 * BREAKING CHANGE: installed latest gatsby version [2.0.20] * chore: updating yarn.lock * refactor: installing retaled package updates * refactor: missing 'prismjs' package needed for 'gatsby-transformer-remark' in v2 * refactor: change .babelrc to gatsby default * refactor: moved layouts to components updated relative imports * refactor: renamed index.jsx to layout.jsx and moved to components folder * refactor: wrapped template pages without layout component * refactor: changed 'children()' to 'children' in layout.jsx * refactor: pass location to Layout component in all templates * refactor: renamed id property of authors to uid | id seems to be a special proberty of nodes and messing with it breaks queries * refactor: deprecated gatsby-link | removed package and updated imports * refactor: explicit import of graphql tag * refactor: Rename boundActionCreators to actions * refactor: Rename pathContext to pageContext * refactor: Change modifyWebpackConfig to onCreateWebpackConfig * docs: Updating to reflect Gatsby 2.0 support * chore: linting JS and most component CSS errors - avoiding changes to layout.css for now * chore(release): 2.0.0
Anyone run into this when trying to run a build?
error Building static HTML for pages failed
See our docs page on debugging HTML builds for help https://goo.gl/yL9lND
The text was updated successfully, but these errors were encountered: