Hi could someone please help me with my first netlify deployment? I’ve been trying to deploy from github, but deploy gets stuck forever on the build process. When I exit out it gives me the error saying it could not locate a index.jsx file in src, even though it its clearly there. Here’s some more details.
netlify site name: ecstatic-darwin-ab812f
Base directory: Not set
Build command: npm run-script build
Publish directory: client/dist/
I am using webpack/babel.
1:09:54 PM: Build ready to start
1:09:56 PM: build-image version: 3031d4c9e432fd7016f6279fc9ad706f9205d845
1:09:56 PM: build-image tag: v3.3.17
1:09:56 PM: buildbot version: 1f35b3abd6e2bf5230d8edf68072840fdec1513f
1:09:56 PM: Fetching cached dependencies
1:09:57 PM: Starting to download cache of 176.8MB
1:09:59 PM: Finished downloading cache in 2.378608686s
1:09:59 PM: Starting to extract cache
1:10:00 PM: Finished extracting cache in 1.580754309s
1:10:00 PM: Finished fetching cache in 4.006310731s
1:10:00 PM: Starting to prepare the repo for build
1:10:01 PM: Preparing Git Reference refs/heads/master
1:10:03 PM: Different publish path detected, going to use the one specified in the Netlify configuration file: 'client/dist' versus 'client/dist/' in the Netlify UI
1:10:03 PM: Starting build script
1:10:03 PM: Installing dependencies
1:10:03 PM: Python version set to 2.7
1:10:04 PM: v12.18.0 is already installed.
1:10:05 PM: Now using node v12.18.0 (npm v6.14.4)
1:10:05 PM: Started restoring cached build plugins
1:10:05 PM: Finished restoring cached build plugins
1:10:05 PM: Attempting ruby version 2.7.1, read from environment
1:10:06 PM: Using ruby version 2.7.1
1:10:06 PM: Using PHP version 5.6
1:10:06 PM: 5.2 is already installed.
1:10:06 PM: Using Swift version 5.2
1:10:06 PM: Started restoring cached node modules
1:10:06 PM: Finished restoring cached node modules
1:10:07 PM: Installing NPM modules using NPM version 6.14.4
1:10:17 PM: > core-js@2.6.11 postinstall /opt/build/repo/node_modules/core-js
1:10:17 PM: > node -e "try{require('./postinstall')}catch(e){}"
1:10:18 PM: > nodemailer@6.4.10 postinstall /opt/build/repo/node_modules/nodemailer
1:10:18 PM: > node -e "try{require('./postinstall')}catch(e){}"
1:10:18 PM: === Nodemailer 6.4.10 ===
1:10:18 PM:
1:10:18 PM: Thank you for using Nodemailer for your email sending needs! While Nodemailer
1:10:18 PM: itself is mostly meant to be a SMTP client there are other related projects in
1:10:18 PM: the Nodemailer project as well.
1:10:18 PM:
1:10:18 PM: > IMAP API ( https://imapapi.com ) is a server application to easily access
1:10:18 PM: IMAP accounts via REST API
1:10:18 PM: > ImapFlow ( https://imapflow.com/ ) is an async IMAP client library for
1:10:18 PM: Node.js
1:10:18 PM: > NodemailerApp ( https://nodemailer.com/app/ ) is a cross platform GUI app to
1:10:18 PM: debug emails
1:10:18 PM: > Project Pending ( https://projectpending.com/ ) allows you to host DNS of
1:10:18 PM: your project domains
1:10:18 PM: > Pending DNS ( https://pendingdns.com/ ) is the DNS server used that powers
1:10:18 PM: Project Pending
1:10:18 PM: > Ethereal Email ( https://ethereal.email/ ) is an email testing service that
1:10:18 PM: accepts all your test emails
1:10:18 PM:
1:10:22 PM: ........
1:10:22 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/watchpack-chokidar2/node_modules/fsevents):
1:10:22 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
1:10:22 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/fsevents):
1:10:22 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
1:10:22 PM: added 662 packages from 437 contributors and audited 667 packages in 15.034s
1:10:23 PM: 9 packages are looking for funding
1:10:23 PM: run `npm fund` for details
1:10:23 PM: found 1 low severity vulnerability
1:10:23 PM: run `npm audit fix` to fix them, or `npm audit` for details
1:10:23 PM: NPM modules installed
1:10:23 PM: Started restoring cached go cache
1:10:23 PM: Finished restoring cached go cache
1:10:23 PM: go version go1.14.4 linux/amd64
1:10:23 PM: go version go1.14.4 linux/amd64
1:10:23 PM: Installing missing commands
1:10:23 PM: Verify run directory
1:10:24 PM:
1:10:24 PM: ┌─────────────────────────────┐
1:10:24 PM: │ Netlify Build │
1:10:24 PM: └─────────────────────────────┘
1:10:24 PM:
1:10:24 PM: ❯ Version
1:10:24 PM: @netlify/build 2.0.10
1:10:24 PM:
1:10:24 PM: ❯ Flags
1:10:24 PM: deployId: 5ef3b31282074f0007e8624d
1:10:24 PM: mode: buildbot
1:10:24 PM:
1:10:24 PM: ❯ Current directory
1:10:24 PM: /opt/build/repo
1:10:24 PM:
1:10:24 PM: ❯ Config file
1:10:24 PM: No config file was defined: using default values.
1:10:24 PM:
1:10:24 PM: ❯ Context
1:10:24 PM: production
1:10:24 PM:
1:10:24 PM: ┌────────────────────────────────┐
1:10:24 PM: │ 1. Build command from settings │
1:10:24 PM: └────────────────────────────────┘
1:10:24 PM:
1:10:24 PM: $ npm run-script build
1:10:24 PM: > bertrandporfolio@1.0.0 build /opt/build/repo
1:10:24 PM: > webpack -d --w
1:10:25 PM: Webpack is watching the files…
1:10:25 PM: (node:1316) DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see https://github.com/webpack/loader-utils/issues/56
1:10:25 PM: parseQuery() will be replaced with getOptions() in the next major version of loader-utils.
1:10:29 PM: Hash: abf0dc8affc04aa7cb52
1:10:29 PM: Version: webpack 2.7.0
1:10:29 PM: Time: 4291ms
1:10:29 PM: Asset Size Chunks Chunk Names
1:10:29 PM: bundle.js 7.14 MB 0 [emitted] [big] main
1:10:29 PM: [0] ./~/react/index.js 190 bytes {0} [built]
1:10:29 PM: [4] ./~/process/browser.js 5.42 kB {0} [built]
1:10:29 PM: [33] ./~/react-dom/index.js 1.36 kB {0} [built]
1:10:29 PM: [83] ./~/react-router-dom/esm/react-router-dom.js 10.3 kB {0} [built]
1:10:29 PM: [91] ./~/redux/es/redux.js 24.2 kB {0} [built]
1:10:29 PM: [150] ./client/src/redux/reducers/burgerMenu.js 412 bytes {0} [built]
1:10:29 PM: [151] ./~/react-redux/es/index.js 776 bytes {0} [built]
1:10:29 PM: [256] ./~/react-redux/es/hooks/useStore.js 1.18 kB {0} [built]
1:10:29 PM: [257] ./~/react-redux/es/utils/batch.js 413 bytes {0} [built]
1:10:29 PM: [258] ./~/react-redux/es/utils/shallowEqual.js 654 bytes {0} [built]
1:10:29 PM: [285] ./client/src/redux/reducers/index.js 436 bytes {0} [built]
1:10:29 PM: [345] ./client/src/index.jsx 1.03 kB {0} [built]
1:10:29 PM: [538] ./~/react-dom/cjs/react-dom.development.js 859 kB {0} [built]
1:10:29 PM: [539] ./~/react-dom/cjs/react-dom.production.min.js 119 kB {0} [built]
1:10:29 PM: [552] ./~/react-redux/es/connect/connect.js 4.98 kB {0} [built]
1:10:29 PM: + 680 hidden modules
1:39:55 PM: Build exceeded maximum allowed runtime
1:39:56 PM: Hash: 195e34558063cc756de5
1:39:56 PM: Version: webpack 2.7.0
1:39:56 PM: Time: 28ms
1:39:56 PM: Asset Size Chunks Chunk Names
1:39:56 PM: bundle.js 3.17 kB 0 [emitted] main
1:39:56 PM: [345] ./client/src/index.jsx 126 bytes {0} [built] [failed] [1 error]
1:39:56 PM: ERROR in ./client/src/index.jsx
1:39:56 PM: Module build failed: Error: ENOENT: no such file or directory, open '/opt/build/repo/client/src/index.jsx'
1:39:58 PM:
1:39:58 PM: (build.command completed in 29m 33.5s)
1:39:58 PM:
1:39:58 PM: ┌─────────────────────────────┐
1:39:58 PM: │ Netlify Build Complete │
1:39:58 PM: └─────────────────────────────┘
1:39:58 PM:
1:39:58 PM: (Netlify Build completed in 29m 33.5s)
1:39:58 PM: Execution timed out after 15m0s
1:39:58 PM: Error running command: Command did not finish within the time limit
1:39:58 PM: Failing build: Failed to build site
1:40:28 PM: Failed to inform the API about a failed build, please retry the build or contact support
1:40:28 PM: Finished processing build request in 30m31.555167465shey @bertrandcodes - so as per that build log, the maximum regular time limit for a build is 15 minutes.
Two things you can try -
And if that doesn’t do the trick, We can extend that time limit to 30 minutes. You’d need to put a credit card into your netlify account so we can automatically bill you for more build minutes should you end up using them before we’d extend your build limit. Let us know if you’d like us to do that!
Do you think time limit is the issue though? My file seems pretty small, with 7 or so pages. There are maybe 15 jpg images and 3 mp4s, but would that cause the build to take over 15 minutes? Also one of the errors was telling me it couldn’t find client/src/index.js when it is clearly there…
hi bertrand, I wouldn’t expect a fairly small site to be having the issues you are describing, no. Let’s try and see if we can fix the issue with the file not found and see if what is really happening is that something is “stuck” or timing out because of that missing file.
You say the file is actually there. is it a case issue?