Bug report

As the title says

Describe the bug

When i build locally, using npm run build, the build loads just fine as it should. I can then run it using npm start and view it on localhost:3000. I then upload the repository to github and go to watch my project fail to deploy as it has countless times while trying to fix the issue. Here is the log that is reported:

23:52:18.923 Retrieving list of deployment files… 23:52:19.086 Downloading 52 deployment files… 23:52:47.935 Installing build runtime… 23:52:48.377 Build runtime installed: 442.214ms 23:52:48.736 Looking up build cache… 23:52:48.766 Build cache not found 23:52:49.132 Installing dependencies… 23:52:58.140 npm WARN portfolio@1.0.0 No description 23:52:58.141 npm WARN portfolio@1.0.0 No repository field. 23:52:58.141 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.12 (node_modules/webpack/node_modules/fsevents): 23:52:58.141 npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.12: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”}) 23:52:58.141 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.12 (node_modules/next/node_modules/fsevents): 23:52:58.141 npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.12: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”}) 23:52:58.141 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/fsevents): 23:52:58.141 npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”}) 23:52:58.143 added 682 packages from 263 contributors in 8.675s 23:52:58.402 14 packages are looking for funding 23:52:58.402 run npm fund for details 23:52:58.443 Running “npm run build” 23:52:58.626 > portfolio@1.0.0 build /zeit/621d0a52 23:52:58.626 > next build 23:52:59.199 Creating an optimized production build… 23:52:59.213 Attention: Next.js now collects completely anonymous telemetry regarding usage. 23:52:59.213 This information is used to shape Next.js’ roadmap and prioritize features. 23:52:59.213 You can learn more, including how to opt-out if you’d not like to participate in this anonymous program, by visiting the following URL: 23:52:59.213 https://nextjs.org/telemetry 23:53:05.505 Failed to compile. 23:53:05.505 ./components/TopBarNavigator/index.js 23:53:05.505 Module not found: Can’t resolve ‘…/…/assets/meAvatar.jpg’ in ‘/zeit/621d0a52/components/TopBarNavigator’ 23:53:05.506 > Build error occurred 23:53:05.507 Error: > Build failed because of webpack errors 23:53:05.507 at build (/zeit/621d0a52/node_modules/next/dist/build/index.js:13:900) 23:53:05.519 npm ERR! code ELIFECYCLE 23:53:05.519 npm ERR! errno 1 23:53:05.520 npm ERR! portfolio@1.0.0 build: next build 23:53:05.520 npm ERR! Exit status 1 23:53:05.520 npm ERR! 23:53:05.520 npm ERR! Failed at the portfolio@1.0.0 build script. 23:53:05.520 npm ERR! This is probably not a problem with npm. There is likely additional logging output above. 23:53:05.523 npm ERR! A complete log of this run can be found in: 23:53:05.523 npm ERR! /zeit/.npm/_logs/2020-04-06T04_53_05_520Z-debug.log 23:53:05.532 Error: Exited with 1 23:53:05.532 at ChildProcess.<anonymous> (/zeit/60d2972f44a2442d/.build-utils/node_modules/@now/build-utils/dist/index.js:31349:24) 23:53:05.532 at ChildProcess.emit (events.js:223:5) 23:53:05.532 at ChildProcess.EventEmitter.emit (domain.js:475:20) 23:53:05.532 at maybeClose (internal/child_process.js:1021:16) 23:53:05.533 at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5) 23:53:07.128 Done with “package.json”

To Reproduce

1. npm run build
2. npm start and view behavior
3. verify the application works the way I want then upload repo to github.
4. go to ZEIT now and view the building process

Expected behavior

expect the build to have no errors

Screenshots

here is my package.json

here is my next.config.js

where the issue is said to occur, but actually occurs at every import

System information

• OS: Windows 10
• Browser chrome
• Version of Next.js:

Additional context

Add any other context about the problem here.