Site deploys but is blank

PLEASE help us help you by writing a good post!

  • We need to know your netlify site name. Example: gifted-antelope-58b104.netlify.app
  • DNS issues? Tell us the custom domain, tell us the error message! We can’t help if we don’t know your domain.
  • Build problems? Link or paste the FULL build log & build settings screenshot
  • Did you try Ask Netlify, our generative AI chatbot, before posting? It pulls info from Support Guides and recent solved forums posts.

The better the post - the faster the answer.


2:57:43 AM: npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@3. I"ll try to do my best with it!
npm WARN deprecated react-particles-js@2.7.1: This package has been deprecated in favor of react-tsparticles.

2:57:43 AM: npm WARN deprecated babel-eslint@9.0.0: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.

2:57:43 AM: npm WARN deprecated eslint-loader@2.1.1: This loader has been deprecated. Please use eslint-webpack-plugin

2:57:43 AM: npm WARN deprecated html-webpack-plugin@4.0.0-alpha.2: please switch to a stable version

2:57:43 AM: npm WARN deprecated fsevents@1.2.4: The v1 package contains DANGEROUS / INSECURE binaries. Upgrade to safe fsevents v2

2:57:44 AM: npm WARN deprecated @babel/plugin-proposal-class-properties@7.3.0: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.

2:57:44 AM: npm WARN deprecated @babel/plugin-proposal-object-rest-spread@7.3.2: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead.

2:57:45 AM: npm WARN deprecated core-js@2.6.4: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.

2:57:45 AM: npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies

2:57:46 AM: npm WARN deprecated node-pre-gyp@0.10.3: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future

2:57:47 AM: npm WARN deprecated acorn-dynamic-import@3.0.0: This is probably built in to whatever tool you"re using. If you still need it… idk
npm WARN deprecated svgo@1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x.

2:57:47 AM: npm WARN deprecated @babel/plugin-proposal-object-rest-spread@7.20.7: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead.

2:57:47 AM: npm WARN deprecated @babel/plugin-proposal-json-strings@7.18.6: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-json-strings instead.

2:57:47 AM: npm WARN deprecated @babel/plugin-proposal-async-generator-functions@7.20.7: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-async-generator-functions instead.

2:57:47 AM: npm WARN deprecated @babel/plugin-proposal-optional-catch-binding@7.18.6: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-catch-binding instead.

2:57:47 AM: npm WARN deprecated @babel/plugin-proposal-unicode-property-regex@7.18.6: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-unicode-property-regex instead.

2:57:48 AM: npm WARN deprecated figgy-pudding@3.5.2: This module is no longer supported.

2:57:48 AM: npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.

2:57:48 AM: npm WARN deprecated fsevents@1.2.13: The v1 package contains DANGEROUS / INSECURE binaries. Upgrade to safe fsevents v2

2:57:48 AM: npm WARN deprecated joi@11.4.0: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).

2:57:49 AM: npm WARN deprecated workbox-google-analytics@3.6.3: It is not compatible with newer versions of GA starting with v4, as long as you are using GAv3 it should be ok, but the package is not longer being maintained

2:57:49 AM: npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See There’s Math.random(), and then there’s Math.random() · V8 for details.

2:57:51 AM: npm WARN deprecated stable@0.1.8: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: Array.prototype.sort() - JavaScript | MDN

2:57:51 AM: npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.

2:57:51 AM: npm WARN deprecated sane@2.5.2: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added

2:57:51 AM: npm WARN deprecated kleur@2.0.2: Please upgrade to kleur@3 or migrate to “ansi-colors” if you prefer the old syntax. Visit https://github.com/lukeed/kleur/releases/tag/v3.0.0\ for migration path(s).

2:57:52 AM: npm WARN deprecated flatten@1.0.3: flatten is deprecated in favor of utility frameworks such as lodash.

2:57:52 AM: npm WARN deprecated hoek@4.3.1: This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.

2:57:52 AM: npm WARN deprecated topo@2.1.1: This module has moved and is now available at @hapi/topo. Please update your dependencies as this version is no longer maintained and may contain bugs and security issues.

2:57:53 AM: npm WARN deprecated source-map-resolve@0.5.3: See GitHub - lydell/source-map-resolve: [DEPRECATED] Resolve the source map and/or sources for a generated file.

2:57:53 AM: npm WARN deprecated abab@2.0.6: Use your platform"s native atob() and btoa() methods instead
npm WARN deprecated domexception@1.0.1: Use your platform"s native DOMException instead
npm WARN deprecated left-pad@1.3.0: use String.prototype.padStart()

2:57:53 AM: npm WARN deprecated request@2.88.2: request has been deprecated, see Request’s Past, Present and Future · Issue #3142 · request/request · GitHub

2:57:53 AM: npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see Request’s Past, Present and Future · Issue #3142 · request/request · GitHub

2:57:54 AM: npm WARN deprecated w3c-hr-time@1.0.2: Use your platform"s native performance.now() and performance.timeOrigin.
npm WARN deprecated source-map-url@0.4.1: See GitHub - lydell/source-map-url: [DEPRECATED] Tools for working with sourceMappingURL comments.

2:57:54 AM: npm WARN deprecated resolve-url@0.2.1: GitHub - lydell/resolve-url: [DEPRECATED] Like Node.js’ `path.resolve`/`url.resolve` for the browser.

2:57:54 AM: npm WARN deprecated urix@0.1.0: Please see GitHub - lydell/urix: [DEPRECATED] Makes Windows-style paths more unix and URI friendly.

2:57:54 AM: npm WARN deprecated har-validator@5.1.5: this library is no longer supported

2:58:08 AM: > core-js@2.6.12 postinstall /opt/build/repo/node_modules/babel-register/node_modules/core-js

2:58:08 AM: > node -e “try{require(”./postinstall")}catch(e){}"

2:58:08 AM: > core-js@2.6.12 postinstall /opt/build/repo/node_modules/babel-runtime/node_modules/core-js

2:58:08 AM: > node -e “try{require(”./postinstall")}catch(e){}"

2:58:08 AM: > core-js@3.36.1 postinstall /opt/build/repo/node_modules/core-js

2:58:08 AM: > node -e “try{require(”./postinstall")}catch(e){}"

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules/react-scripts/node_modules/fsevents):

2:58:09 AM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/chokidar/node_modules/fsevents):

2:58:09 AM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/watchpack/node_modules/chokidar/node_modules/fsevents):

2:58:09 AM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.3: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})

2:58:09 AM: npm WARN @babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining@7.23.3 requires a peer of @babel/core@^7.13.0 but none is installed. You must install peer dependencies yourself.

2:58:09 AM: npm WARN @babel/plugin-transform-class-static-block@7.23.4 requires a peer of @babel/core@^7.12.0 but none is installed. You must install peer dependencies yourself.

2:58:09 AM: npm WARN babel-plugin-polyfill-corejs2@0.4.10 requires a peer of @babel/core@^7.4.0 || ^8.0.0-0 <8.0.0 but none is installed. You must install peer dependencies yourself.

2:58:09 AM: npm WARN babel-plugin-polyfill-corejs3@0.9.0 requires a peer of @babel/core@^7.4.0 || ^8.0.0-0 <8.0.0 but none is installed. You must install peer dependencies yourself.

2:58:09 AM: npm WARN @babel/helper-define-polyfill-provider@0.5.0 requires a peer of @babel/core@^7.4.0 || ^8.0.0-0 <8.0.0 but none is installed. You must install peer dependencies yourself.

2:58:09 AM: npm WARN babel-plugin-polyfill-regenerator@0.5.5 requires a peer of @babel/core@^7.4.0 || ^8.0.0-0 <8.0.0 but none is installed. You must install peer dependencies yourself.

2:58:09 AM: npm WARN @babel/helper-define-polyfill-provider@0.5.0 requires a peer of @babel/core@^7.4.0 || ^8.0.0-0 <8.0.0 but none is installed. You must install peer dependencies yourself.

2:58:09 AM: npm WARN @babel/helper-define-polyfill-provider@0.6.1 requires a peer of @babel/core@^7.4.0 || ^8.0.0-0 <8.0.0 but none is installed. You must install peer dependencies yourself.

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: abbrev@1.1.1 (node_modules/fsevents/node_modules/abbrev):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/abbrev” → “/opt/build/repo/node_modules/fsevents/node_modules/.abbrev.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: ansi-regex@2.1.1 (node_modules/fsevents/node_modules/ansi-regex):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/ansi-regex” → “/opt/build/repo/node_modules/fsevents/node_modules/.ansi-regex.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: aproba@1.2.0 (node_modules/fsevents/node_modules/aproba):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/aproba” → “/opt/build/repo/node_modules/fsevents/node_modules/.aproba.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: balanced-match@1.0.0 (node_modules/fsevents/node_modules/balanced-match):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/balanced-match” → “/opt/build/repo/node_modules/fsevents/node_modules/.balanced-match.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: chownr@1.0.1 (node_modules/fsevents/node_modules/chownr):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/chownr” → “/opt/build/repo/node_modules/fsevents/node_modules/.chownr.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: code-point-at@1.1.0 (node_modules/fsevents/node_modules/code-point-at):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/code-point-at” → “/opt/build/repo/node_modules/fsevents/node_modules/.code-point-at.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: concat-map@0.0.1 (node_modules/fsevents/node_modules/concat-map):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/concat-map” → “/opt/build/repo/node_modules/fsevents/node_modules/.concat-map.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: console-control-strings@1.1.0 (node_modules/fsevents/node_modules/console-control-strings):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/console-control-strings” → “/opt/build/repo/node_modules/fsevents/node_modules/.console-control-strings.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: core-util-is@1.0.2 (node_modules/fsevents/node_modules/core-util-is):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/core-util-is” → “/opt/build/repo/node_modules/fsevents/node_modules/.core-util-is.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: deep-extend@0.5.1 (node_modules/fsevents/node_modules/deep-extend):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/deep-extend” → “/opt/build/repo/node_modules/fsevents/node_modules/.deep-extend.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: delegates@1.0.0 (node_modules/fsevents/node_modules/delegates):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/delegates” → “/opt/build/repo/node_modules/fsevents/node_modules/.delegates.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: detect-libc@1.0.3 (node_modules/fsevents/node_modules/detect-libc):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/detect-libc” → “/opt/build/repo/node_modules/fsevents/node_modules/.detect-libc.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fs.realpath@1.0.0 (node_modules/fsevents/node_modules/fs.realpath):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/fs.realpath” → “/opt/build/repo/node_modules/fsevents/node_modules/.fs.realpath.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: has-unicode@2.0.1 (node_modules/fsevents/node_modules/has-unicode):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/has-unicode” → “/opt/build/repo/node_modules/fsevents/node_modules/.has-unicode.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: inherits@2.0.3 (node_modules/fsevents/node_modules/inherits):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/inherits” → “/opt/build/repo/node_modules/fsevents/node_modules/.inherits.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: ini@1.3.5 (node_modules/fsevents/node_modules/ini):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/ini” → “/opt/build/repo/node_modules/fsevents/node_modules/.ini.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: isarray@1.0.0 (node_modules/fsevents/node_modules/isarray):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/isarray” → “/opt/build/repo/node_modules/fsevents/node_modules/.isarray.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: minimist@0.0.8 (node_modules/fsevents/node_modules/minimist):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/minimist” → “/opt/build/repo/node_modules/fsevents/node_modules/.minimist.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: ms@2.0.0 (node_modules/fsevents/node_modules/ms):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/ms” → “/opt/build/repo/node_modules/fsevents/node_modules/.ms.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: npm-bundled@1.0.3 (node_modules/fsevents/node_modules/npm-bundled):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/npm-bundled” → “/opt/build/repo/node_modules/fsevents/node_modules/.npm-bundled.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: number-is-nan@1.0.1 (node_modules/fsevents/node_modules/number-is-nan):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/number-is-nan” → “/opt/build/repo/node_modules/fsevents/node_modules/.number-is-nan.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: object-assign@4.1.1 (node_modules/fsevents/node_modules/object-assign):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/object-assign” → “/opt/build/repo/node_modules/fsevents/node_modules/.object-assign.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: os-homedir@1.0.2 (node_modules/fsevents/node_modules/os-homedir):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/os-homedir” → “/opt/build/repo/node_modules/fsevents/node_modules/.os-homedir.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: os-tmpdir@1.0.2 (node_modules/fsevents/node_modules/os-tmpdir):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/os-tmpdir” → “/opt/build/repo/node_modules/fsevents/node_modules/.os-tmpdir.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: path-is-absolute@1.0.1 (node_modules/fsevents/node_modules/path-is-absolute):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/path-is-absolute” → “/opt/build/repo/node_modules/fsevents/node_modules/.path-is-absolute.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: process-nextick-args@2.0.0 (node_modules/fsevents/node_modules/process-nextick-args):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/process-nextick-args” → “/opt/build/repo/node_modules/fsevents/node_modules/.process-nextick-args.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: minimist@1.2.0 (node_modules/fsevents/node_modules/rc/node_modules/minimist):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/rc/node_modules/minimist” → “/opt/build/repo/node_modules/fsevents/node_modules/rc/node_modules/.minimist.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: safe-buffer@5.1.1 (node_modules/fsevents/node_modules/safe-buffer):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/safe-buffer” → “/opt/build/repo/node_modules/fsevents/node_modules/.safe-buffer.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: safer-buffer@2.1.2 (node_modules/fsevents/node_modules/safer-buffer):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/safer-buffer” → “/opt/build/repo/node_modules/fsevents/node_modules/.safer-buffer.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: sax@1.2.4 (node_modules/fsevents/node_modules/sax):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/sax” → “/opt/build/repo/node_modules/fsevents/node_modules/.sax.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: semver@5.5.0 (node_modules/fsevents/node_modules/semver):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/semver” → “/opt/build/repo/node_modules/fsevents/node_modules/.semver.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: set-blocking@2.0.0 (node_modules/fsevents/node_modules/set-blocking):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/set-blocking” → “/opt/build/repo/node_modules/fsevents/node_modules/.set-blocking.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: signal-exit@3.0.2 (node_modules/fsevents/node_modules/signal-exit):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/signal-exit” → “/opt/build/repo/node_modules/fsevents/node_modules/.signal-exit.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: strip-json-comments@2.0.1 (node_modules/fsevents/node_modules/strip-json-comments):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/strip-json-comments” → “/opt/build/repo/node_modules/fsevents/node_modules/.strip-json-comments.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: util-deprecate@1.0.2 (node_modules/fsevents/node_modules/util-deprecate):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/util-deprecate” → “/opt/build/repo/node_modules/fsevents/node_modules/.util-deprecate.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: wrappy@1.0.2 (node_modules/fsevents/node_modules/wrappy):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/wrappy” → “/opt/build/repo/node_modules/fsevents/node_modules/.wrappy.DELETE”

2:58:09 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: yallist@3.0.2 (node_modules/fsevents/node_modules/yallist):

2:58:09 AM: npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename “/opt/build/repo/node_modules/fsevents/node_modules/yallist” → “/opt/build/repo/node_modules/fsevents/node_modules/.yallist.DELETE”
2:58:09 AM: added 1917 packages from 695 contributors and audited 1987 packages in 26.835s
2:58:09 AM: 107 packages are looking for funding
2:58:09 AM: run npm fund for details
2:58:09 AM: found 224 vulnerabilities (20 low, 112 moderate, 71 high, 21 critical)
2:58:09 AM: run npm audit fix to fix them, or npm audit for details
2:58:09 AM: npm packages installed
2:58:10 AM: Successfully installed dependencies

Building:
2:58:24 AM: Line 53: img elements must have an alt prop, either with meaningful text, or an empty string for decorative images jsx-a11y/alt-text
2:58:24 AM: Line 62: img elements must have an alt prop, either with meaningful text, or an empty string for decorative images jsx-a11y/alt-text
2:58:24 AM: Line 63: img elements must have an alt prop, either with meaningful text, or an empty string for decorative images jsx-a11y/alt-text
2:58:24 AM: Line 64: img elements must have an alt prop, either with meaningful text, or an empty string for decorative images jsx-a11y/alt-text
2:58:24 AM: Line 96: img elements must have an alt prop, either with meaningful text, or an empty string for decorative images jsx-a11y/alt-text
2:58:24 AM: Line 97: img elements must have an alt prop, either with meaningful text, or an empty string for decorative images jsx-a11y/alt-text
2:58:24 AM: Line 98: img elements must have an alt prop, either with meaningful text, or an empty string for decorative images jsx-a11y/alt-text
2:58:24 AM: ./src/Architectural_Design/Body_Main/Body.js
2:58:24 AM: Line 3: “Transition” is defined but never used no-unused-vars
2:58:24 AM: Line 3: “animated” is defined but never used no-unused-vars
2:58:24 AM: ./src/Architectural_Design/views/Projects/Proj_dets/cart.js
2:58:24 AM: Line 4: “Sunset” is defined but never used no-unused-vars
2:58:24 AM: Line 26: “backdrop” is assigned a value but never used no-unused-vars
2:58:24 AM: Line 51: img elements must have an alt prop, either with meaningful text, or an empty string for decorative images jsx-a11y/alt-text
2:58:24 AM: Line 59: img elements must have an alt prop, either with meaningful text, or an empty string for decorative images jsx-a11y/alt-text
2:58:24 AM: ./src/Architectural_Design/views/TestView/Testfile.js
2:58:24 AM: Line 4: “Header” is defined but never used no-unused-vars
2:58:24 AM: ./src/Architectural_Design/views/Home/Home.js
2:58:24 AM: Line 5: “Rez” is defined but never used no-unused-vars
2:58:24 AM: Line 26: “backdrop” is assigned a value but never used no-unused-vars
2:58:24 AM: ./src/index.js
2:58:24 AM: Line 5: “Projects” is defined but never used no-unused-vars
2:58:24 AM: Search for the keywords to learn more about each warning.
2:58:24 AM: To ignore, add // eslint-disable-next-line to the line before.
2:58:24 AM: File sizes after gzip:
2:58:24 AM: 78.49 KB build/static/js/2.da53f298.chunk.js
2:58:24 AM: 10.21 KB build/static/js/main.a756aae7.chunk.js
2:58:24 AM: 3.45 KB build/static/css/main.44c170e6.chunk.css
2:58:24 AM: 762 B build/static/js/runtime~main.a8a9905a.js
2:58:24 AM: The project was built assuming it is hosted at the server root.
2:58:24 AM: You can control this with the homepage field in your package.json.
2:58:24 AM: For example, add this to build it for GitHub Pages:
2:58:24 AM: “homepage” : “http://myname.github.io/myapp”,
2:58:24 AM: The build folder is ready to be deployed.
2:58:24 AM: You may serve it with a static server:
2:58:24 AM: npm install -g serve
2:58:24 AM: serve -s build
2:58:24 AM: Find out more about deployment here:
2:58:24 AM: create-react-app/packages/react-scripts/template/README.md at main · facebook/create-react-app · GitHub
2:58:24 AM: ​
2:58:24 AM: Warning: some redirects have syntax errors:
2:58:24 AM: ​
2:58:24 AM: Could not parse redirect line 1:
2:58:24 AM: /* npm/index.html 200
The destination path/URL must start with “/”, “http:” or “https:”

Hi team,
I am trying to make changes to my website that I launched 4 years ago. However trying to re-deploy the site through netlify is throwing the above errors. I have limited understand of netlify and react at this point. How do I go about fixing all these problems? Netlify successfully deploys but the page comes up blank.

https://65f93742f78c6c7c27bd1f88--armghanhaider.netlify.app/

@shiftraza The site is blank because it’s dying at runtime with the JavaScript error visible in the browser’s developer console.

Debugging your project specific code is “out of scope” for this forum.

The easiest way to debug it will be to run it locally.

Hi @nathanmartin thanks for your message. My site works in local host. It is just failing to deploy/appears blank when I try to deploy it through netlify.

@shiftraza That may be the case, but it’s likely you’re only running your development server.

You should try running the precise build command you’re running on Netlify, (not your develop command), then serve the output as it instructs with npx serve -s build, as per:

The end result should be the same as on Netlify.

Netlify isn’t changing the JavaScript that your build produces.