Hi Perry,
Yes, this build works locally (I haven’t actually changed anything since I built and deployed it using the Netlify CLI a few weeks back - after I got the note on Twitter the EPIPE error was fixed, I was curious to see if I could turn back on my auto deploys, so I just tried rebuilding my unchanged “master” branch).
Here’s the package.json - I’m using Node v14.16 and Yarn.
{
"name": "paigeniedringhaus.com",
"description": "Personal website of Paige Niedringhaus running on Gatsby and React",
"version": "1.1.0",
"author": "Paige Niedringhaus <hellopaigen@gmail.com>",
"repository": "https://github.com/paigen11/paigeniedringhaus.com.git",
"dependencies": {
"@fortawesome/fontawesome-svg-core": "^6.1.1",
"@fortawesome/free-brands-svg-icons": "^6.1.1",
"@fortawesome/free-solid-svg-icons": "^6.1.1",
"@fortawesome/react-fontawesome": "^0.1.9",
"classnames": "^2.2.6",
"gatsby": "4.12.1",
"gatsby-cli": "4.12.1",
"gatsby-plugin-catch-links": "4.12.1",
"gatsby-plugin-feed": "4.12.1",
"gatsby-plugin-google-analytics": "4.12.1",
"gatsby-plugin-google-fonts": "^1.0.1",
"gatsby-plugin-google-gtag": "4.12.1",
"gatsby-plugin-image": "^2.12.1",
"gatsby-plugin-lodash": "^5.12.1",
"gatsby-plugin-mailgo": "^0.12.2",
"gatsby-plugin-manifest": "4.12.1",
"gatsby-plugin-nprogress": "4.12.1",
"gatsby-plugin-offline": "^5.12.1",
"gatsby-plugin-react-helmet": "^5.12.1",
"gatsby-plugin-react-helmet-canonical-urls": "^1.4.0",
"gatsby-plugin-sass": "^5.12.1",
"gatsby-plugin-sharp": "4.12.1",
"gatsby-plugin-sitemap": "^5.12.1",
"gatsby-plugin-twitter": "4.12.1",
"gatsby-remark-autolink-headers": "^5.12.1",
"gatsby-remark-code-titles": "^1.1.0",
"gatsby-remark-copy-linked-files": "^5.12.1",
"gatsby-remark-embed-video": "^3.1.1",
"gatsby-remark-images": "^6.12.1",
"gatsby-remark-prismjs": "^6.12.1",
"gatsby-remark-relative-images": "^2.0.2",
"gatsby-remark-responsive-iframe": "^5.12.1",
"gatsby-source-filesystem": "4.12.1",
"gatsby-transformer-remark": "^5.12.1",
"gatsby-transformer-sharp": "4.12.1",
"lodash": "^4.17.15",
"moment": "^2.24.0",
"node-sass": "^4.0.1",
"prismjs": "^1.22.0",
"react": "^18.0.0",
"react-dom": "^18.0.0",
"react-headroom": "^3.1.0",
"react-helmet": "^6.1.0",
"react-share": "^4.1.0",
"react-twitter-widgets": "^1.7.1",
"url-join": "^4.0.0"
},
"devDependencies": {
"cli-glob": "^0.1.0",
"eslint": "^6.8.0",
"eslint-config-airbnb": "^18.1.0",
"eslint-config-prettier": "^6.10.1",
"eslint-plugin-import": "^2.20.2",
"eslint-plugin-jsx-a11y": "^6.2.1",
"eslint-plugin-react": "^7.19.0",
"gatsby-plugin-netlify": "^4.3.0",
"gh-pages": "^2.2.0",
"prettier": "^2.0.2",
"remark-cli": "^8.0.0",
"remark-preset-lint-recommended": "^4.0.0",
"stylelint": "^13.2.1",
"stylelint-config-prettier": "^8.0.1",
"stylelint-config-standard": "^20.0.0",
"write-good": "^1.0.1"
},
"keywords": [
"paige niedringhaus",
"development",
"dev",
"tech",
"articles",
"blog",
"developer",
"frontend",
"react",
"gatsby"
],
"license": "MIT",
"main": "n/a",
"scripts": {
"develop": "gatsby develop",
"dev": "npm run develop",
"serve": "gatsby serve",
"build": "gatsby build",
"build:pp": "gatsby build --prefix-paths",
"build:gh": "npm run clean && npm run build:pp && gh-pages -d public",
"clean": "rm -rf public && rm -rf .cache",
"lint:js": "eslint --ext .js,.jsx .",
"lint:md": "remark content/",
"write-good": "write-good $(glob 'content/posts/**/*.md')",
"format:js": "prettier '**/*.{js,jsx}' --write",
"format:styles": "prettier '**/*.{css,scss}' --write"
},
"remarkConfig": {
"plugins": [
"remark-preset-lint-recommended"
]
},
"volta": {
"node": "14.16.1",
"npm": "7.20.1",
"yarn": "1.22.17"
}
}
And yes, I did run “clear cache and redeploy” to get a fresh build.