New to Netlify, need help deploying my website, info attached

shivermotion · October 10, 2022, 4:26am

netlify name: https://fightertoolkit.netlify.app
custom domain: www.fightertoolkit.com
New to Netlify and trying to deploy my site. Current errors.

10:55:01 PM: Build ready to start
10:55:04 PM: build-image version: 9289b698a503f132b265bd089ab40ce1d6f9e65e (focal)
10:55:04 PM: build-image tag: v4.12.0
10:55:04 PM: buildbot version: c87074660cd9a4568c0ac759bc083987e94204b3
10:55:04 PM: Fetching cached dependencies
10:55:04 PM: Failed to fetch cache, continuing with build
10:55:04 PM: Starting to prepare the repo for build
10:55:04 PM: No cached dependencies found. Cloning fresh repo
10:55:04 PM: git clone [https://]github.[com]/shivermotion/fighter-tool-kit
10:55:05 PM: Preparing Git Reference refs/heads/master
10:55:05 PM: Parsing package.json dependencies
10:55:06 PM: Starting build script
10:55:06 PM: Installing dependencies
10:55:06 PM: Python version set to 2.7
10:55:06 PM: v16.17.1 is already installed.
10:55:07 PM: Now using node v16.17.1 (npm v8.15.0)
10:55:07 PM: Started restoring cached build plugins
10:55:07 PM: Finished restoring cached build plugins
10:55:07 PM: Attempting ruby version 2.7.2, read from environment
10:55:07 PM: Using ruby version 2.7.2
10:55:07 PM: Using PHP version 8.0
10:55:08 PM: No npm workspaces detected
10:55:08 PM: Started restoring cached node modules
10:55:08 PM: Finished restoring cached node modules
10:55:08 PM: Installing NPM modules using NPM version 8.15.0
10:55:08 PM: npm WARN config tmp This setting is no longer used. npm stores temporary files in a special
10:55:08 PM: npm WARN config location in the cache, and they are managed by
10:55:08 PM: npm WARN config
10:55:08 PM: npm WARN config tmp This setting is no longer used. npm stores temporary files in a special
10:55:08 PM: npm WARN config location in the cache, and they are managed by
10:55:08 PM: npm WARN config
10:55:13 PM: 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:
10:55:16 PM: npm WARN deprecated svgo@1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
10:55:25 PM: added 1655 packages, and audited 1656 packages in 17s
10:55:25 PM: 220 packages are looking for funding
10:55:25 PM: run npm fund for details
10:55:25 PM: 6 high severity vulnerabilities
10:55:25 PM: To address all issues (including breaking changes), run:
10:55:25 PM: npm audit fix --force
10:55:25 PM: Run npm audit for details.
10:55:25 PM: NPM modules installed
10:55:26 PM: npm WARN config tmp This setting is no longer used. npm stores temporary files in a special
10:55:26 PM: npm WARN config location in the cache, and they are managed by
10:55:26 PM: npm WARN config
10:55:26 PM: Started restoring cached go cache
10:55:26 PM: Finished restoring cached go cache
10:55:26 PM: Installing Go version 1.17 (requested 1.17)
10:55:30 PM: unset GOOS;
10:55:30 PM: unset GOARCH;
10:55:30 PM: export GOROOT=‘/opt/buildhome/.gimme/versions/go1.17.linux.amd64’;
10:55:30 PM: export PATH=“/opt/buildhome/.gimme/versions/go1.17.linux.amd64/bin:${PATH}”;
10:55:30 PM: go version >&2;
10:55:30 PM: export GIMME_ENV=“/opt/buildhome/.gimme/env/go1.17.linux.amd64.env”
10:55:30 PM: go version go1.17 linux/amd64
10:55:30 PM: Installing missing commands
10:55:30 PM: Verify run directory
10:55:31 PM:
10:55:31 PM: ────────────────────────────────────────────────────────────────
10:55:31 PM: Netlify Build
10:55:31 PM: ────────────────────────────────────────────────────────────────
10:55:31 PM:
10:55:31 PM: ❯ Version
10:55:31 PM: @netlify/build 27.20.1
10:55:31 PM:
10:55:31 PM: ❯ Flags
10:55:31 PM: baseRelDir: true
10:55:31 PM: buildId: 63439795ccdf941ea93419db
10:55:31 PM: deployId: 63439795ccdf941ea93419dd
10:55:31 PM:
10:55:31 PM: ❯ Current directory
10:55:31 PM: /opt/build/repo
10:55:31 PM:
10:55:31 PM: ❯ Config file
10:55:31 PM: No config file was defined: using default values.
10:55:31 PM:
10:55:31 PM: ❯ Context
10:55:31 PM: production
10:55:31 PM:
10:55:31 PM: ────────────────────────────────────────────────────────────────
10:55:31 PM: 1. Build command from Netlify app
10:55:31 PM: ────────────────────────────────────────────────────────────────
10:55:31 PM:
10:55:31 PM: $ npm run build
10:55:31 PM: npm WARN config tmp This setting is no longer used. npm stores temporary files in a special
10:55:31 PM: npm WARN config location in the cache, and they are managed by
10:55:31 PM: npm WARN config
10:55:31 PM: > fighter-tool-kit@0.1.0 build
10:55:31 PM: > react-scripts build
10:55:32 PM: Creating an optimized production build…
10:56:29 PM: Failed to compile.
10:56:29 PM:
10:56:29 PM: Cannot find module ‘sass’
10:56:29 PM: Require stack:
10:56:29 PM: - /opt/build/repo/node_modules/sass-loader/dist/utils.js
10:56:29 PM: - /opt/build/repo/node_modules/sass-loader/dist/index.js
10:56:29 PM: - /opt/build/repo/node_modules/sass-loader/dist/cjs.js
10:56:29 PM: - /opt/build/repo/node_modules/loader-runner/lib/loadLoader.js
10:56:29 PM: - /opt/build/repo/node_modules/loader-runner/lib/LoaderRunner.js
10:56:29 PM: - /opt/build/repo/node_modules/webpack/lib/NormalModule.js
10:56:29 PM: - /opt/build/repo/node_modules/webpack-manifest-plugin/dist/index.js
10:56:29 PM: - /opt/build/repo/node_modules/react-scripts/config/webpack.config.js
10:56:29 PM: - /opt/build/repo/node_modules/react-scripts/scripts/build.js
10:56:29 PM:
10:56:29 PM: ────────────────────────────────────────────────────────────────
10:56:29 PM: “build.command” failed
10:56:29 PM: ────────────────────────────────────────────────────────────────
10:56:29 PM:
10:56:29 PM: Error message
10:56:29 PM: Command failed with exit code 1: npm run build
10:56:29 PM:
10:56:29 PM: Error location
10:56:29 PM: In Build command from Netlify app:
10:56:29 PM: npm run build
10:56:29 PM:
10:56:29 PM: Resolved config
10:56:29 PM: build:
10:56:29 PM: command: npm run build
10:56:29 PM: commandOrigin: ui
10:56:29 PM: environment:
10:56:29 PM: - CI
10:56:29 PM: - NPM_FLAGS
10:56:29 PM: publish: /opt/build/repo/build
10:56:29 PM: publishOrigin: ui
10:56:30 PM: Caching artifacts
10:56:30 PM: Started saving node modules
10:56:30 PM: Finished saving node modules
10:56:30 PM: Started saving build plugins
10:56:30 PM: Finished saving build plugins
10:56:30 PM: Started saving pip cache
10:56:30 PM: Finished saving pip cache
10:56:30 PM: Started saving emacs cask dependencies
10:56:30 PM: Finished saving emacs cask dependencies
10:56:30 PM: Started saving maven dependencies
10:56:30 PM: Finished saving maven dependencies
10:56:30 PM: Started saving boot dependencies
10:56:30 PM: Finished saving boot dependencies
10:56:30 PM: Started saving rust rustup cache
10:56:30 PM: Finished saving rust rustup cache
10:56:30 PM: Started saving go dependencies
10:56:30 PM: Finished saving go dependencies
10:56:30 PM: Build failed due to a user error: Build script returned non-zero exit code: 2
10:56:30 PM: Creating deploy upload records
10:56:30 PM: Failing build: Failed to build site
10:56:30 PM: Failed during stage ‘building site’: Build script returned non-zero exit code: 2
10:56:31 PM: Finished processing build request in 1m26.82706808s

current env variables
env-settings-netlify

jszynal · October 11, 2022, 2:19am

Just first glance here Shiver but do you have sass listed in your package.json as a dependency?

10:56:29 PM: Cannot find module ‘sass’

shivermotion · October 11, 2022, 4:07am

SOLVED : site is now live and showing. There multiple things that needed to be adjusted including

having homepage, start url, and my router paths all matching.
having crossorigin=“use-credentials” and href=“manifest.json” included in my manifest link in public index header.
making sure my modules were installed on master.
4.setting env variables on netflify to NPM_Flags --dev-peer-legacy.

Update: My problem was I needed to set NPM_FLAGS --dev-peer-legacy. Site now deploys and goes live, but is blank…

Hey @jszynal , here is my current sass
see pic attached:

hillary · October 11, 2022, 2:27pm

Thanks for coming back and sharing your solution! This will help future forums members who encounter something similar.

jszynal · October 11, 2022, 4:07pm

@shivermotion your screenshot shows the package-lock.json with the sass references in there but those may be peer dependencies. Can you confirm you’ve got sass listed in your package.json file as a dependency?