8:05:03 AM: Netlify Build
8:05:03 AM: ────────────────────────────────────────────────────────────────
8:05:03 AM:
8:05:03 AM: ❯ Version
8:05:03 AM: @netlify/build 29.15.3
8:05:03 AM:
8:05:03 AM: ❯ Flags
8:05:03 AM: baseRelDir: true
8:05:03 AM: buildId: 64ac01f1b0e6cb18765fe720
8:05:03 AM: deployId: 64ac01f1b0e6cb18765fe722
8:05:03 AM:
8:05:03 AM: ❯ Current directory
8:05:03 AM: /opt/build/repo
8:05:03 AM:
8:05:03 AM: ❯ Config file
8:05:03 AM: No config file was defined: using default values.
8:05:03 AM:
8:05:03 AM: ❯ Context
8:05:03 AM: production
8:05:03 AM:
8:05:03 AM: Build command from Netlify app
8:05:03 AM: ────────────────────────────────────────────────────────────────
8:05:03 AM:
8:05:03 AM: $ npm run build
8:05:06 AM: Failed during stage ‘building site’: Build script returned non-zero exit code: 2 (Search results for '"non-zero exit code: 2"' - Netlify Support Forums)
8:05:03 AM: > fetchapi@0.0.0 build
8:05:03 AM: > tsc && vite build
8:05:05 AM: src/App.tsx(7,3): error TS6133: ‘useNavigate’ is declared but its value is never read.
8:05:05 AM: src/App.tsx(9,19): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘./pages/login/Login.js’?
8:05:05 AM: src/App.tsx(10,20): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘./componets/Layout.js’?
8:05:05 AM: src/App.tsx(11,18): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘./pages/home/Home.js’?
8:05:05 AM: src/App.tsx(12,30): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘./context/AuthContext.js’?
8:05:05 AM: src/App.tsx(13,32): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘./componets/ProtectedRoute.js’?
8:05:05 AM: src/App.tsx(14,22): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘./pages/DogMatch.js’?
8:05:05 AM: src/App.tsx(15,19): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘./pages/Error.js’?
8:05:05 AM: src/componets/Layout.tsx(2,20): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘./navbar/NavBar.js’?
8:05:05 AM: src/componets/PagePagination.tsx(1,41): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘…/data/data.js’?
8:05:05 AM: src/componets/PagePagination.tsx(61,9): error TS2345: Argument of type ‘Element’ is not assignable to parameter of type ‘never’.
8:05:05 AM: src/componets/PagePagination.tsx(61,10): error TS2604: JSX element type ‘PageItem’ does not have any construct or call signatures.
8:05:05 AM: src/componets/PagePagination.tsx(61,10): error TS2786: ‘PageItem’ cannot be used as a JSX component.
8:05:05 AM: Its type ‘typeof import(/opt/build/repo/node_modules/react-bootstrap/esm/PageItem)’ is not a valid JSX element type.
8:05:05 AM: src/componets/PagePagination.tsx(76,6): error TS2604: JSX element type ‘Pagination’ does not have any construct or call signatures.
8:05:05 AM: src/componets/PagePagination.tsx(76,6): error TS2786: ‘Pagination’ cannot be used as a JSX component.
8:05:05 AM: Its type ‘typeof import(/opt/build/repo/node_modules/react-bootstrap/esm/Pagination)’ is not a valid JSX element type.
8:05:05 AM: src/componets/PagePagination.tsx(77,19): error TS2339: Property ‘Prev’ does not exist on type ‘typeof import(/opt/build/repo/node_modules/react-bootstrap/esm/Pagination)’.
8:05:05 AM: src/componets/PagePagination.tsx(79,19): error TS2339: Property ‘Next’ does not exist on type ‘typeof import(/opt/build/repo/node_modules/react-bootstrap/esm/Pagination)’.
8:05:05 AM: src/componets/ProtectedRoute.tsx(2,32): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘…/context/AuthContext.js’?
8:05:05 AM: src/componets/ProtectedRoute.tsx(3,1): error TS6133: ‘ReactNode’ is declared but its value is never read.
8:05:05 AM: src/componets/navbar/NavBar.tsx(2,32): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘…/…/context/AuthContext.js’?
8:05:05 AM: src/componets/navbar/NavBar.tsx(4,28): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘…/…/data/dataAuthUsage.js’?
8:05:05 AM: src/context/AuthContext.tsx(6,17): error TS6133: ‘val’ is declared but its value is never read.
8:05:05 AM: src/context/AuthContext.tsx(8,17): error TS6133: ‘data’ is declared but its value is never read.
8:05:05 AM: src/data/dataAuthUsage.ts(1,40): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘./data.js’?
8:05:05 AM: src/data/dogData.ts(1,40): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘./data.js’?
8:05:05 AM: src/data/locationData.ts(2,40): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘./data.js’?
8:05:05 AM: src/main.tsx(3,17): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘./App.js’?
8:05:05 AM: src/pages/DogMatch.tsx(1,31): error TS6133: ‘useRef’ is declared but its value is never read.
8:05:05 AM: src/pages/DogMatch.tsx(2,38): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘…/data/dogData.js’?
8:05:05 AM: src/pages/DogMatch.tsx(3,21): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘./dog cards/DogData.js’?
8:05:05 AM: src/pages/DogMatch.tsx(4,32): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘…/context/AuthContext.js’?
8:05:05 AM: src/pages/DogMatch.tsx(8,19): error TS6133: ‘props’ is declared but its value is never read.
8:05:05 AM: src/pages/dog cards/DogCards.tsx(1,21): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘./DogData.js’?
8:05:05 AM: src/pages/home/Home.tsx(3,44): error TS6133: ‘getMatch’ is declared but its value is never read.
8:05:05 AM: src/pages/home/Home.tsx(3,60): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘…/…/data/dogData.js’?
8:05:05 AM: src/pages/home/Home.tsx(6,3): error TS6133: ‘Max_Page’ is declared but its value is never read.
8:05:05 AM: src/pages/home/Home.tsx(7,3): error TS6133: ‘Data_Per_Page’ is declared but its value is never read.
8:05:05 AM: src/pages/home/Home.tsx(8,3): error TS6133: ‘Filters’ is declared but its value is never read.
8:05:05 AM: src/pages/home/Home.tsx(13,8): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘…/…/data/data.js’?
8:05:05 AM: src/pages/home/Home.tsx(14,27): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘…/…/componets/SearchFilters.js’?
8:05:05 AM: src/pages/home/Home.tsx(15,22): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘…/dog cards/DogCards.js’?
8:05:05 AM: src/pages/home/Home.tsx(16,28): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘…/…/componets/PagePagination.js’?
8:05:05 AM: src/pages/home/Home.tsx(22,8): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘…/…/data/locationData.js’?
8:05:05 AM: src/pages/home/Home.tsx(24,32): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘…/…/context/AuthContext.js’?
8:05:05 AM: src/pages/home/Home.tsx(64,19): error TS2345: Argument of type ‘any’ is not assignable to parameter of type ‘never’.
8:05:05 AM: src/pages/home/Home.tsx(64,43): error TS2339: Property ‘value’ does not exist on type ‘never’.
8:05:05 AM: src/pages/home/Home.tsx(129,42): error TS2339: Property ‘value’ does not exist on type ‘never’.
8:05:05 AM: src/pages/home/Home.tsx(190,14): error TS2604: JSX element type ‘Alert’ does not have any construct or call signatures.
8:05:05 AM: src/pages/home/Home.tsx(190,14): error TS2786: ‘Alert’ cannot be used as a JSX component.
8:05:05 AM: Its type ‘typeof import(/opt/build/repo/node_modules/react-bootstrap/esm/Alert)’ is not a valid JSX element type.
8:05:05 AM: src/pages/home/Home.tsx(236,16): error TS2604: JSX element type ‘Alert’ does not have any construct or call signatures.
8:05:05 AM: src/pages/home/Home.tsx(236,16): error TS2786: ‘Alert’ cannot be used as a JSX component.
8:05:05 AM: Its type ‘typeof import(/opt/build/repo/node_modules/react-bootstrap/esm/Alert)’ is not a valid JSX element type.
8:05:05 AM: src/pages/login/Login.tsx(4,32): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘…/…/context/AuthContext.js’?
8:05:05 AM: src/pages/login/Login.tsx(5,27): error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when ‘–moduleResolution’ is ‘node16’ or ‘nodenext’. Did you mean ‘…/…/data/dataAuthUsage.js’?
8:05:05 AM: src/pages/login/Login.tsx(11,8): error TS6196: ‘loginProps’ is declared but never used.
8:05:05 AM: src/pages/login/Login.tsx(51,15): error TS6133: ‘e’ is declared but its value is never read.
8:05:05 AM:
8:05:05 AM: build.command failed
8:05:05 AM: ────────────────────────────────────────────────────────────────
8:05:05 AM:
8:05:05 AM: Error message
8:05:05 AM: Command failed with exit code 2: npm run build (Search results for '"non-zero exit code: 2"' - Netlify Support Forums)
8:05:05 AM:
8:05:05 AM: Error location
8:05:05 AM: In Build command from Netlify app:
8:05:05 AM: npm run build
8:05:05 AM:
8:05:05 AM: Resolved config
8:05:05 AM: build:
8:05:05 AM: command: npm run build
8:05:05 AM: commandOrigin: ui
8:05:05 AM: environment:
8:05:05 AM: - CI
8:05:05 AM: - DEPRECATED
8:05:05 AM: publish: /opt/build/repo/dist
8:05:05 AM: publishOrigin: ui
8:05:06 AM: Build failed due to a user error: Build script returned non-zero exit code: 2
8:05:06 AM: Failing build: Failed to build site
8:05:07 AM: Finished processing build request in 16.026s
Hi there, glad you found us 
: before we can help you, we need a little more information on the issues you are facing.
First, have you looked through this resource? It is a compilation of all of our build and deploy resources. This is a good starting point.
If you have worked through those guides and are still encountering issues please share the following information:
- the name of your build instance: “example-jones.netlify.com”
- what you have already tried
- any error messages you have received in your terminal window or in the developer console
@chrisfoehser2 Your build is throwing a lot of warnings.
By default warnings are treated as errors and will cause the build to fail.
To set CI from the default of true to false you can adjust your Build command from npm run build to CI= npm run build