react-animations | 🎊 A collection of animations for inline style libraries | Animation library

While typescript is able to infer types most of the time, it cannot do it for react props, even for children props.

To remove all the XXX implicitly has an 'any' type in your code, you need to add a React.FC (stands for Functional Component) for your components using children and React.FC when using your own props.

For your three current component you would have:

MenuItem.tsx

This may be a silly answer. Try checking whether the task is running or any other programs interfereing the app, like an antivirus.

There's not much debug in the question however, to me, it seems that you are using some dependencies outside React's scope, which may potentially block React's hydration process, which may explain the problem described. For example, using Leaflet instead of React's Leaflet or (depending on its implementation) Bootstrap instead of React's Boostrap.

You should be able to change all React-unfriendly modules to React's ones without too much effort and that should fix your problems.

Keep in mind that if your project "work in develop and breaks in build" doesn't mean that your project work or stops working, it just means that is working under certain and specific circumstances. Basically, and summarizing (to avoid extending the answer), gatsby develop uses the browser as an interpreter, where there are, among other things, global objects like window or document. However, gatsby build occurs in the Node server, where at the build time, there are not global objects because there are not even created yet, that the main reason why you may face a different behavior between both scenarios but doesn't mean that the project stopped working magically.

You can read further details in the Overview of Gatsby Build Process.

Another option, linked with blocking React's hydration, is that some component may be blocking that process because of its own behavior. Be careful when using global objects like window or document (or when importing modules that uses it), they use should be always be wrapped inside the following condition, as you can see from the docs:

When referencing window in a React component.

OK, I figured out the issue. I thought the error was telling me that path was undefined. When it fact it was saying the variables passed into path.join() were undefined. And that was because I forgot to add in my .env file to the root so it could grab those variables. Whoops!

A styled component uses string interpolation (Templates literals) with a functions that takes the props of the component as the first parameter. So, you could do something like,

Change the homepage path : "homepage": "https://yourusername.github.io/your-project-name",

Firstly, make sure you are copying the same package-lock.json file that you use to install deps locally, to make sure you have the same dependency tree in your container as you do locally.

COPY package.json package-lock.json /app/

Then, make sure that you are matching the same node/npm version as you run locally (replace 12 with the major version you are running, be it 10, 12, 14 or whatever):

FROM node:12

Each node version is bundled with a specific npm version (latest 12 version comes with npm 6.14.6), you can find the bundled NPM version int he changelogs, https://github.com/nodejs/node/tree/master/doc/changelogs

Additionally, instead of running npm install, you might wanna run npm ci in the container. The latter skips any checks for discrepancy between the lock file and your package.json file and just installs the locked dependency tree, which is not only faster, but will also match your local dep tree exactly.

EDIT:

In addition, this line:

COPY . /app

Would also overwrite node_modules unless you have ignored it via .dockerignore or similar.

Easiest would probably be to add a .dockerignore file to the same folder as your Dockerfile and add lines stating: