"Module not found" without any changes to code! What's wrong?

My site was working and deploying just fine as recent as 3 weeks ago. Nothing has been changed since, but now it won’t deploy. I get hit by the error:

Module not found: Error: Can't resolve 'services/contentfulData/aboutPage.json' in '/opt/build/repo/pages'

I’m new to everything and learning more by the day. I received control of my site and I’m slowly learning how it’s built. I have been alerted that the site uses Node.js 8, but that doesn’t seem like it will be a problem until January (I don’t think it’s related to my current issue, but unsure).

I’m thinking this is probably due to some dependency, but I am not sure. Does this error imply something I’m missing?

Here are the dependencies from package.json. However, I have a package-lock.json as well.

"dependencies": {
"@babel/cli": "^7.1.2",
"@babel/node": "^7.0.0",
"@babel/plugin-proposal-decorators": "^7.1.2",
"@babel/preset-env": "^7.1.0",
"@zeit/next-css": "^1.0.1",
"@zeit/next-less": "^1.0.1",
"antd": "^3.10.3",
"aws-amplify": "^1.1.9",
"aws-amplify-react": "^2.1.3",
"babel-plugin-import": "^1.9.1",
"babel-plugin-inline-import": "^3.0.0",
"babel-plugin-inline-react-svg": "^0.5.4",
"babel-plugin-styled-components": "^1.8.0",
"contentful": "^7.0.5",
"cross-env": "^5.2.0",
"date-fns": "^1.29.0",
"dotenv": "^6.1.0",
"download": "^7.1.0",
"express": "^4.16.4",
"fast-safe-stringify": "^2.0.6",
"file-loader": "^2.0.0",
"fs-extra": "^7.0.0",
"less": "^3.8.1",
"less-plugin-clean-css": "^1.5.1",
"lodash": "^4.17.11",
"lqip": "^2.1.0",
"markdown-to-jsx": "^6.8.3",
"netlify-lambda": "^0.4.0",
"next": "^7.0.2",
"next-offline": "^3.3.4",
"next-routes": "^1.4.2",
"path-match": "^1.2.4",
"purched-antd-icons": "^0.2.2",
"react": "^16.8.6",
"react-dom": "^16.8.6",
"react-ga": "^2.5.3",
"react-google-recaptcha": "^1.0.4",
"react-instantsearch": "^5.3.2",
"react-mailchimp-subscribe": "^2.0.2",
"react-stack-grid": "^0.7.1",
"react-styled-flexboxgrid": "^2.6.0",
"resolve": "^1.8.1",
"sitemap": "^2.1.0",
"sqip": "^0.3.3",
"styled-components": "^3.4.10",
"styled-media-query": "^2.0.2",
"uuid": "^3.3.2",
"workbox-webpack-plugin": "^3.6.3"

"devDependencies": {
    "@zeit/next-bundle-analyzer": "^0.1.2",
    "babel-eslint": "^9.0.0",
    "babel-plugin-css-modules-transform": "^1.6.1",
    "eslint": "^5.8.0",
    "eslint-config-airbnb": "^17.1.0",
    "eslint-config-prettier": "^3.1.0",
    "eslint-config-standard": "^12.0.0",
    "eslint-config-standard-react": "^7.0.2",
    "eslint-plugin-import": "^2.14.0",
    "eslint-plugin-jsx-a11y": "^6.1.2",
    "eslint-plugin-node": "^7.0.1",
    "eslint-plugin-prettier": "^3.0.0",
    "eslint-plugin-promise": "^4.0.1",
    "eslint-plugin-react": "^7.11.1",
    "eslint-plugin-standard": "^4.0.0",
    "serve": "^10.0.2"

I know it’s kind of a shot in the dark and I truly appreciate any assistance! You guys are wizards and something may jump out at you that I’d completely miss.


Heya @psillow and sorry to hear about the struggle! At first blush that sounds like a case sensitivity issue - our build system is case sensitive and most folks choose to standardize in both filenames and references to filenames on 100% lowercase. Anything that npm installs will almost certainly be all lowercase, for instance. Could you see if you can find any references in your code with the capital letters and try lowercasing them?

Not sure why that would break without any related change, but perhaps there was a seemingly innocuous change that changed case?