Showing logs for build greencapitaltrade/flash/pr-245 #1 stage from-build-pack and container prepare
2026/06/19 19:17:51 Entrypoint initialization

Showing logs for build greencapitaltrade/flash/pr-245 #1 stage from-build-pack and container place-scripts
2026/06/19 19:18:00 Decoded script /tekton/scripts/script-0-42pfv
2026/06/19 19:18:00 Decoded script /tekton/scripts/script-1-spq5s
2026/06/19 19:18:00 Decoded script /tekton/scripts/script-2-wvj5z
2026/06/19 19:18:00 Decoded script /tekton/scripts/script-3-rrzhf
2026/06/19 19:18:00 Decoded script /tekton/scripts/script-4-45p8q
2026/06/19 19:18:00 Decoded script /tekton/scripts/script-5-rmq6h
2026/06/19 19:18:00 Decoded script /tekton/scripts/script-7-kxxq8
2026/06/19 19:18:00 Decoded script /tekton/scripts/script-8-rbz5h

Showing logs for build greencapitaltrade/flash/pr-245 #1 stage from-build-pack and container working-dir-initializer

Showing logs for build greencapitaltrade/flash/pr-245 #1 stage from-build-pack and container step-git-clone
git cloning url: https://github.com/greencapitaltrade/flash.git version refs/pull/245/head:PR-245@458ec508f813c0494113bcf48516203033cc490a to dir: source
Cloning into 'source'...
From https://github.com/greencapitaltrade/flash
 * [new ref]         refs/pull/245/head -> PR-245
Switched to branch 'PR-245'
HEAD is now at 458ec50 test: add unit test stage to PR pipeline
checked out revision: refs/pull/245/head:PR-245@458ec508f813c0494113bcf48516203033cc490a to dir: source

Showing logs for build greencapitaltrade/flash/pr-245 #1 stage from-build-pack and container step-git-merge
setup git user  email jenkins-x@googlegroups.com
Using SHAs from PULL_REFS=main:1bee894183e45adf8b518845fb587261a0a7654a,245:458ec508f813c0494113bcf48516203033cc490a:refs/pull/245/head
using base branch main and base sha 1bee894183e45adf8b518845fb587261a0a7654a
merging sha: 458ec508f813c0494113bcf48516203033cc490a

Showing logs for build greencapitaltrade/flash/pr-245 #1 stage from-build-pack and container step-jx-variables
WARNING: no $GIT_SECRET_MOUNT_PATH environment variable set
about to run: git clone --no-checkout --filter=blob:none --depth=1 https://github.com/greencapitaltrade/mcu.git /tmp/jx-git-3748085752 in dir /tmp
Cloning into '/tmp/jx-git-3748085752'...
about to run: git sparse-checkout set --no-cone jx-requirements.yml .jx/gitops/source-config.yaml in dir /tmp/jx-git-3748085752
about to run: git checkout in dir /tmp/jx-git-3748085752
Your branch is up to date with 'origin/main'.
export APP_NAME='flash'
export BRANCH_NAME='PR-245'
export BUILD_NUMBER='1'
export DOCKERFILE_PATH='Dockerfile'
export DOCKER_REGISTRY='417755753340.dkr.ecr.ap-south-1.amazonaws.com'
export DOCKER_REGISTRY_ORG='greencapitaltrade'
export DOMAIN='gc-t.in'
about to run: git rev-parse --abbrev-ref HEAD in dir .
main
export GIT_BRANCH='main'
export JENKINS_X_URL='https://dashboard-jx.gc-t.in/greencapitaltrade/flash/PR-245/1'
export JX_CHART_REPOSITORY='http://jenkins-x-chartmuseum.jx.svc.cluster.local:8080'
export KANIKO_FLAGS='--skip-unused-stages --snapshotMode=redo'
export MINK_AS='tekton-bot'
version file VERSION does not exist
export MINK_IMAGE='417755753340.dkr.ecr.ap-south-1.amazonaws.com/greencapitaltrade/flash:0.0.0-PR-245-1-SNAPSHOT'
export NAMESPACE_SUB_DOMAIN='-jx.'
export PIPELINE_KIND='pullrequest'
export PUSH_CONTAINER_REGISTRY='417755753340.dkr.ecr.ap-south-1.amazonaws.com'
export REPO_NAME='flash'
export REPO_OWNER='greencapitaltrade'
version file VERSION does not exist
export VERSION='0.0.0-PR-245-1-SNAPSHOT'
added variables to file: .jx/variables.sh
added variables to file: .jx/variables.sh

Showing logs for build greencapitaltrade/flash/pr-245 #1 stage from-build-pack and container step-build-yarn-install
! Corepack is about to download https://repo.yarnpkg.com/4.5.0/packages/yarnpkg-cli/bin/yarn.js
➤ YN0000: · Yarn 4.5.0
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed in 0s 515ms
➤ YN0000: ┌ Post-resolution validation
➤ YN0086: │ Some peer dependencies are incorrectly met by dependencies; run yarn explain peer-requirements for details.
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0066: │ typescript@patch:typescript@npm%3A5.8.3#optional!builtin<compat/typescript>::version=5.8.3&hash=8c6c40: Cannot apply hunk #1
➤ YN0066: │ typescript@patch:typescript@npm%3A5.9.3#optional!builtin<compat/typescript>::version=5.9.3&hash=8c6c40: Cannot apply hunk #1
➤ YN0000: └ Completed in 41s 332ms
➤ YN0000: ┌ Link step
➤ YN0007: │ @biomejs/biome@npm:1.9.4 must be built because it never has been before or the last one failed
➤ YN0007: │ esbuild@npm:0.21.5 must be built because it never has been before or the last one failed
➤ YN0007: │ esbuild@npm:0.27.2 must be built because it never has been before or the last one failed
➤ YN0007: │ esbuild@npm:0.27.7 must be built because it never has been before or the last one failed
➤ YN0007: │ esbuild@npm:0.14.47 must be built because it never has been before or the last one failed
➤ YN0007: │ sharp@npm:0.34.5 must be built because it never has been before or the last one failed
➤ YN0007: │ esbuild@npm:0.25.10 must be built because it never has been before or the last one failed
➤ YN0007: │ @swc/core@npm:1.15.11 [36772] must be built because it never has been before or the last one failed
➤ YN0007: │ unrs-resolver@npm:1.11.1 must be built because it never has been before or the last one failed
➤ YN0007: │ starter-free@workspace:. must be built because it never has been before or the last one failed
➤ YN0000: │ starter-free@workspace:. STDOUT Tamagui dependencies look good ✅
➤ YN0000: │ starter-free@workspace:. STDOUT API package built
➤ YN0000: │ starter-free@workspace:. STDOUT [baseline-browser-mapping] The data in this module is over two months old.  To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
➤ YN0000: │ starter-free@workspace:. STDOUT built @my/config in 401 ms
➤ YN0000: │ starter-free@workspace:. STDOUT [baseline-browser-mapping] The data in this module is over two months old.  To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
➤ YN0000: │ starter-free@workspace:. STDOUT built @my/ui in 542 ms
➤ YN0000: │ starter-free@workspace:. STDOUT Done in 4s 200ms
➤ YN0000: └ Completed in 28s 394ms
➤ YN0000: · Done with warnings in 1m 11s

Showing logs for build greencapitaltrade/flash/pr-245 #1 stage from-build-pack and container step-unit-tests

 RUN  v2.1.9 /workspace/source

 ✓ packages/app/features/asset/hooks/__tests__/useAssetTelemetry.test.ts (19 tests) 66ms
 ❯ apps/next/__tests__/components/geofences-page.test.tsx (18 tests | 18 failed) 64ms
   × GeofencesPage component > renders without crashing 29ms
     → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"?
If you need to partially mock a module, you can use "importOriginal" helper inside:

   × GeofencesPage component > shows loading spinner when loading with no data 3ms
     → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"?
If you need to partially mock a module, you can use "importOriginal" helper inside:

   × GeofencesPage component > shows Zone Directory header 3ms
     → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"?
If you need to partially mock a module, you can use "importOriginal" helper inside:

   × GeofencesPage component > renders stat card labels 2ms
     → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"?
If you need to partially mock a module, you can use "importOriginal" helper inside:

   × GeofencesPage component > default active tab shows only enabled geofences 3ms
     → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"?
If you need to partially mock a module, you can use "importOriginal" helper inside:

   × GeofencesPage component > clicking All tab shows all geofences 2ms
     → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"?
If you need to partially mock a module, you can use "importOriginal" helper inside:

   × GeofencesPage component > search filters geofences by name 2ms
     → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"?
If you need to partially mock a module, you can use "importOriginal" helper inside:

   × GeofencesPage component > no search matches shows appropriate message 2ms
     → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"?
If you need to partially mock a module, you can use "importOriginal" helper inside:

   × GeofencesPage component > empty geofences shows no geofences yet message 2ms
     → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"?
If you need to partially mock a module, you can use "importOriginal" helper inside:

   × GeofencesPage component > toggle switch calls updateGeofence 2ms
     → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"?
If you need to partially mock a module, you can use "importOriginal" helper inside:

   × GeofencesPage component > Create Zone button navigates to /vehicles 1ms
     → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"?
If you need to partially mock a module, you can use "importOriginal" helper inside:

   × GeofencesPage component > export button is disabled when no geofences 1ms
     → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"?
If you need to partially mock a module, you can use "importOriginal" helper inside:

   × GeofencesPage component > renders map placeholder 1ms
     → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"?
If you need to partially mock a module, you can use "importOriginal" helper inside:

   × GeofencesPage component > geofence card shows type label for circle with radius 2ms
     → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"?
If you need to partially mock a module, you can use "importOriginal" helper inside:

   × GeofencesPage component > geofence card shows vehicle count 2ms
     → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"?
If you need to partially mock a module, you can use "importOriginal" helper inside:

   × GeofencesPage component > loading with existing data does not show spinner 2ms
     → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"?
If you need to partially mock a module, you can use "importOriginal" helper inside:

   × GeofencesPage component > null data renders empty state 2ms
     → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"?
If you need to partially mock a module, you can use "importOriginal" helper inside:

   × GeofencesPage component > alerts text shows Entry for entry-only geofence 2ms
     → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"?
If you need to partially mock a module, you can use "importOriginal" helper inside:

 ✓ packages/ui/src/__tests__/TeamSelector.test.tsx (10 tests) 133ms
stderr | packages/ui/src/__tests__/TeamSelector.test.tsx
Not implemented: navigation to another Document

 ❯ apps/next/__tests__/components/replay-page.test.tsx (0 test)
stderr | apps/next/__tests__/components/error-pages.test.tsx > 404 Not Found Page > renders 404 heading
React does not recognize the `lineHeight` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `lineheight` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `textAlign` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `textalign` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `maxWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `maxwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `backgroundColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `backgroundcolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderRadius` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderradius` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `marginTop` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `margintop` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `alignItems` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `alignitems` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `justifyContent` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `justifycontent` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `marginBottom` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `marginbottom` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `textTransform` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `texttransform` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `bordercolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `minWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `minwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `hoverStyle` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `hoverstyle` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `minHeight` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `minheight` instead. If you accidentally passed it from a parent component, remove it from the DOM element.

stderr | apps/next/__tests__/components/create-team-client.test.tsx > CreateTeamPageClient > renders without crashing
Invalid value for prop `icon` on <button> tag. Either remove it from the element, or pass a string or number value to keep it in the DOM. For details, see https://react.dev/link/attribute-behavior 
React does not recognize the `alignItems` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `alignitems` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `bordercolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `maxWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `maxwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `backgroundColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `backgroundcolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.

stdout | apps/next/__tests__/components/create-team-client.test.tsx > CreateTeamPageClient > submitting form calls createTeam with team name
Team created successfully: { id: 1, name: 'Test' }

stdout | apps/next/__tests__/components/create-team-client.test.tsx > CreateTeamPageClient > trims whitespace from team name before submitting
Team created successfully: { id: 1, name: 'Test' }

 ✓ apps/next/__tests__/components/create-team-client.test.tsx (15 tests) 129ms
stderr | apps/next/__tests__/components/error-pages.test.tsx > 500 Error Page > renders error heading
React does not recognize the `paddingHorizontal` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddinghorizontal` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `paddingVertical` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddingvertical` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderBottomWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderbottomwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderBottomColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderbottomcolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.

stderr | apps/next/__tests__/components/error-pages.test.tsx > 403 Forbidden Page > renders 403 heading
React does not recognize the `marginVertical` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `marginvertical` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `paddingBottom` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddingbottom` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `flexWrap` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `flexwrap` instead. If you accidentally passed it from a parent component, remove it from the DOM element.

 ❯ apps/next/__tests__/components/error-pages.test.tsx (23 tests | 2 failed) 444ms
   × 404 Not Found Page > has quick navigation links 24ms
     → expected false to be true // Object.is equality
   × 403 Forbidden Page > shows role subtitles 47ms
     → expected false to be true // Object.is equality
stderr | apps/next/__tests__/components/iot-device-types-screen.test.tsx > IoTDeviceTypesScreen > renders without crashing
React does not recognize the `justifyContent` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `justifycontent` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `alignItems` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `alignitems` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `flexWrap` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `flexwrap` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
Unknown event handler property `onChangeText`. It will be ignored.
React does not recognize the `placeholderTextColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `placeholdertextcolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `backgroundColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `backgroundcolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `paddingHorizontal` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddinghorizontal` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `focusStyle` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `focusstyle` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `minWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `minwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `bordercolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderRadius` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderradius` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `focusWithinStyle` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `focuswithinstyle` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `paddingVertical` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddingvertical` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `hoverStyle` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `hoverstyle` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `textAlign` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `textalign` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `minHeight` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `minheight` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `maxWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `maxwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `alignSelf` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `alignself` instead. If you accidentally passed it from a parent component, remove it from the DOM element.

 ✓ apps/next/__tests__/components/iot-device-types-screen.test.tsx (9 tests) 237ms
stderr | apps/next/__tests__/components/challan-list-screen.test.tsx > ChallanListScreen > renders without crashing
React does not recognize the `alignItems` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `alignitems` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `paddingHorizontal` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddinghorizontal` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderRadius` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderradius` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `backgroundColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `backgroundcolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `hoverStyle` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `hoverstyle` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `justifyContent` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `justifycontent` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
Unknown event handler property `onChangeText`. It will be ignored.
React does not recognize the `borderWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `minWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `minwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
Unknown event handler property `onValueChange`. It will be ignored.
React does not recognize the `flexWrap` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `flexwrap` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `paddingVertical` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddingvertical` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `numberOfLines` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `numberoflines` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `pressStyle` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `pressstyle` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `marginLeft` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `marginleft` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `bordercolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.

stderr | apps/next/__tests__/components/challan-list-screen.test.tsx > ChallanListScreen > shows empty state when no challans
React does not recognize the `textAlign` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `textalign` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `marginTop` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `margintop` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `minHeight` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `minheight` instead. If you accidentally passed it from a parent component, remove it from the DOM element.

 ✓ apps/next/__tests__/components/challan-list-screen.test.tsx (9 tests) 278ms
 ❯ apps/next/__tests__/components/fleet-live-tracking-screen.test.tsx (8 tests | 8 failed) 46ms
   × LiveTrackingScreen > renders without crashing 27ms
     → Cannot read properties of undefined (reading 'length')
   × LiveTrackingScreen > shows Vehicles header 3ms
     → Cannot read properties of undefined (reading 'length')
   × LiveTrackingScreen > shows LIVE badge 3ms
     → Cannot read properties of undefined (reading 'length')
   × LiveTrackingScreen > renders vehicle registrations 2ms
     → Cannot read properties of undefined (reading 'length')
   × LiveTrackingScreen > shows status counts 4ms
     → Cannot read properties of undefined (reading 'length')
   × LiveTrackingScreen > renders map wrapper 2ms
     → Cannot read properties of undefined (reading 'length')
   × LiveTrackingScreen > shows no vehicles message when filtered empty 3ms
     → Cannot read properties of undefined (reading 'length')
   × LiveTrackingScreen > shows speed for vehicles 2ms
     → Cannot read properties of undefined (reading 'length')
 ✓ apps/next/__tests__/components/teams-client.test.tsx (3 tests) 30ms
 ❯ apps/next/__tests__/components/vehicle-tracking-screen.test.tsx (0 test)
stderr | apps/next/__tests__/components/geofence-drawing-screen.test.tsx > GeofenceDrawingScreen > renders without crashing
React does not recognize the `marginLeft` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `marginleft` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `backgroundColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `backgroundcolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `bordercolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `maxHeight` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `maxheight` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderRightWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderrightwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderRightColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderrightcolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.

 ❯ apps/next/__tests__/components/geofence-drawing-screen.test.tsx (7 tests | 1 failed) 90ms
   × GeofenceDrawingScreen > shows Vehicle Info section 14ms
     → expected false to be true // Object.is equality
 ❯ apps/next/__tests__/components/voltcred-vehicle-detail-screen.test.tsx (0 test)
 ✓ packages/ui/src/__tests__/DatePicker.test.tsx (10 tests) 116ms
 ❯ apps/next/__tests__/components/voltcred-vehicle-list-screen.test.tsx (0 test)
 ❯ apps/next/__tests__/components/vehicle-assignment-screen.test.tsx (0 test)
stderr | apps/next/__tests__/components/gatepass-list-screen.test.tsx > GatepassListScreen > renders without crashing
React does not recognize the `alignItems` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `alignitems` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `paddingHorizontal` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddinghorizontal` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderRadius` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderradius` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `backgroundColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `backgroundcolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `hoverStyle` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `hoverstyle` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `justifyContent` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `justifycontent` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `minWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `minwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `flexWrap` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `flexwrap` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
Unknown event handler property `onChangeText`. It will be ignored.
React does not recognize the `borderWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
Unknown event handler property `onValueChange`. It will be ignored.
React does not recognize the `paddingVertical` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddingvertical` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `numberOfLines` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `numberoflines` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `pressStyle` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `pressstyle` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `bordercolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.

 ✓ apps/next/__tests__/components/gatepass-list-screen.test.tsx (9 tests) 269ms
 ❯ apps/next/__tests__/components/vehicle-iot-settings-screen.test.tsx (0 test)
 ❯ apps/next/__tests__/components/settings-client.test.tsx (0 test)
stderr | apps/next/__tests__/components/fleet-operations-screen.test.tsx > OperationsScreen > renders without crashing
React does not recognize the `alignItems` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `alignitems` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `textTransform` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `texttransform` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `justifyContent` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `justifycontent` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `alignSelf` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `alignself` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `backgroundColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `backgroundcolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `minHeight` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `minheight` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderRadius` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderradius` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `shadowOffset` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `shadowoffset` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `shadowOpacity` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `shadowopacity` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `shadowRadius` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `shadowradius` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `hoverStyle` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `hoverstyle` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `pressStyle` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `pressstyle` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
Invalid attribute name: `$md`
Invalid attribute name: `$lg`
React does not recognize the `flexWrap` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `flexwrap` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `paddingHorizontal` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddinghorizontal` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `bordercolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `marginTop` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `margintop` instead. If you accidentally passed it from a parent component, remove it from the DOM element.

 ❯ apps/next/__tests__/components/fleet-operations-screen.test.tsx (9 tests | 1 failed) 358ms
   × OperationsScreen > shows Fleet Operations header 65ms
     → expected false to be true // Object.is equality
stderr | apps/next/__tests__/components/trip-detail-screen.test.tsx > TripDetailScreen > renders without crashing
React does not recognize the `borderRadius` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderradius` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `backgroundColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `backgroundcolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `bordercolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `hoverStyle` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `hoverstyle` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `paddingHorizontal` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddinghorizontal` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `paddingVertical` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddingvertical` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `alignItems` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `alignitems` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `minWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `minwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `flexWrap` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `flexwrap` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `paddingTop` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddingtop` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `justifyContent` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `justifycontent` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `minHeight` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `minheight` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `textAlign` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `textalign` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `flexDirection` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `flexdirection` instead. If you accidentally passed it from a parent component, remove it from the DOM element.

 ✓ apps/next/__tests__/components/trip-detail-screen.test.tsx (8 tests) 230ms
 ❯ apps/next/__tests__/components/maintenance-client.test.tsx (0 test)
stderr | apps/next/__tests__/components/violations-list-screen.test.tsx > ViolationsListScreen > renders without crashing
React does not recognize the `alignItems` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `alignitems` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `paddingHorizontal` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddinghorizontal` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderRadius` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderradius` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `backgroundColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `backgroundcolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `hoverStyle` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `hoverstyle` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `justifyContent` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `justifycontent` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `flexWrap` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `flexwrap` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `bordercolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
Unknown event handler property `onChangeText`. It will be ignored.
React does not recognize the `minWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `minwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
Unknown event handler property `onValueChange`. It will be ignored.
React does not recognize the `paddingVertical` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddingvertical` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `numberOfLines` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `numberoflines` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `pressStyle` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `pressstyle` instead. If you accidentally passed it from a parent component, remove it from the DOM element.

 ✓ apps/next/__tests__/components/violations-list-screen.test.tsx (8 tests) 213ms
 ❯ apps/next/__tests__/components/documents-client.test.tsx (0 test)
stderr | apps/next/__tests__/components/driver-performance-screen.test.tsx > DriverPerformanceScreen > renders without crashing
React does not recognize the `backgroundColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `backgroundcolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `bordercolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `alignItems` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `alignitems` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `justifyContent` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `justifycontent` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `flexWrap` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `flexwrap` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `textTransform` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `texttransform` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `marginBottom` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `marginbottom` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `minWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `minwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderRadius` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderradius` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `paddingLeft` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddingleft` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `paddingVertical` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddingvertical` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `paddingHorizontal` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddinghorizontal` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `textAlign` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `textalign` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderBottomWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderbottomwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderBottomColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderbottomcolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `iconAfter` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `iconafter` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `maxWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `maxwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `alignSelf` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `alignself` instead. If you accidentally passed it from a parent component, remove it from the DOM element.

 ❯ apps/next/__tests__/components/driver-performance-screen.test.tsx (10 tests | 1 failed) 407ms
   × DriverPerformanceScreen > shows fleet average comparison 39ms
     → expected false to be true // Object.is equality
 ✓ apps/next/__tests__/components/team-detail-client.test.tsx (7 tests) 78ms
 ❯ apps/next/__tests__/components/events-client.test.tsx (0 test)
stderr | apps/next/__tests__/components/trip-list-screen.test.tsx > TripListScreen > renders without crashing
React does not recognize the `alignItems` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `alignitems` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `paddingHorizontal` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddinghorizontal` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderRadius` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderradius` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `backgroundColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `backgroundcolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `hoverStyle` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `hoverstyle` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `pressStyle` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `pressstyle` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `justifyContent` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `justifycontent` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `flexWrap` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `flexwrap` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
Unknown event handler property `onChangeText`. It will be ignored.
React does not recognize the `borderWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `bordercolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `minWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `minwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `paddingVertical` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddingvertical` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `numberOfLines` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `numberoflines` instead. If you accidentally passed it from a parent component, remove it from the DOM element.

 ❯ apps/next/__tests__/components/trip-list-screen.test.tsx (7 tests | 1 failed) 278ms
   × TripListScreen > shows Fleet Trips header 40ms
     → expected false to be true // Object.is equality
stderr | apps/next/__tests__/components/voltcred-trip-list-screen.test.tsx > VoltCredTripListScreen > renders without crashing
React does not recognize the `alignItems` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `alignitems` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderRadius` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderradius` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `minHeight` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `minheight` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `minWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `minwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `justifyContent` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `justifycontent` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `hoverStyle` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `hoverstyle` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `paddingHorizontal` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddinghorizontal` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `paddingBottom` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddingbottom` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `backgroundColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `backgroundcolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderBottomWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderbottomwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderBottomColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderbottomcolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `textDecorationLine` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `textdecorationline` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `marginTop` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `margintop` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
Received `true` for a non-boolean attribute `pressable`.

If you want to write it to the DOM, pass a string instead: pressable="true" or pressable={value.toString()}.
React does not recognize the `paddingTop` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddingtop` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderTopWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `bordertopwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderTopColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `bordertopcolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `paddingVertical` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddingvertical` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `bordercolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
Invalid attribute name: `$md`
React does not recognize the `showsVerticalScrollIndicator` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `showsverticalscrollindicator` instead. If you accidentally passed it from a parent component, remove it from the DOM element.

 ✓ apps/next/__tests__/components/voltcred-trip-list-screen.test.tsx (7 tests) 160ms
 ✓ packages/app/features/asset/components/__tests__/IoTDeviceCard.test.tsx (6 tests) 94ms
 ❯ apps/next/__tests__/components/vehicle-models-screen.test.tsx (0 test)
stderr | apps/next/__tests__/components/tag-management-screen.test.tsx > TagManagementScreen > renders without crashing
React does not recognize the `justifyContent` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `justifycontent` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `alignItems` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `alignitems` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `backgroundColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `backgroundcolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
Unknown event handler property `onChangeText`. It will be ignored.
Unknown event handler property `onValueChange`. It will be ignored.
React does not recognize the `textAlign` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `textalign` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
Received `true` for a non-boolean attribute `circular`.

If you want to write it to the DOM, pass a string instead: circular="true" or circular={value.toString()}.
React does not recognize the `borderWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `borderColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `bordercolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `flexWrap` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `flexwrap` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
Received `true` for a non-boolean attribute `multiline`.

If you want to write it to the DOM, pass a string instead: multiline="true" or multiline={value.toString()}.
React does not recognize the `numberOfLines` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `numberoflines` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
Received `true` for a non-boolean attribute `modal`.

If you want to write it to the DOM, pass a string instead: modal="true" or modal={value.toString()}.
Unknown event handler property `onOpenChange`. It will be ignored.
React does not recognize the `snapPoints` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `snappoints` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `dismissOnSnapToBottom` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `dismissonsnaptobottom` instead. If you accidentally passed it from a parent component, remove it from the DOM element.

 ✓ apps/next/__tests__/components/tag-management-screen.test.tsx (6 tests) 162ms
 ✓ apps/next/__tests__/components/driver-management-client.test.tsx (5 tests) 39ms
stderr | apps/next/__tests__/components/payment-tracking-screen.test.tsx > PaymentTrackingScreen > renders without crashing
React does not recognize the `justifyContent` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `justifycontent` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `alignItems` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `alignitems` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
React does not recognize the `backgroundColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `backgroundcolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
Unknown event handler property `onChangeText`. It will be ignored.
Unknown event handler property `onValueChange`. It will be ignored.
React does not recognize the `textAlign` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `textalign` instead. If you accidentally passed it from a parent component, remove it from the DOM element.

 ✓ apps/next/__tests__/components/payment-tracking-screen.test.tsx (5 tests) 103ms
 ✓ apps/next/__tests__/components/routes-client.test.tsx (3 tests) 46ms
 ❯ apps/next/__tests__/components/vehicles-client.test.tsx (0 test)
 ✓ apps/next/__tests__/components/members-client.test.tsx (3 tests) 54ms
 ✓ packages/app/features/asset/utils/__tests__/replay-utils.test.ts (34 tests) 33ms
 ✓ packages/app/features/asset/utils/__tests__/reportDateRange.test.ts (19 tests) 8ms
 ✓ packages/app/features/asset/utils/__tests__/geofence.test.ts (11 tests) 9ms
 ❯ apps/next/__tests__/components/vehicles-_client.test.tsx (0 test)
 ✓ apps/next/__tests__/components/user-client.test.tsx (3 tests) 39ms
 ✓ packages/app/features/asset/utils/__tests__/geofence-utils.test.ts (18 tests) 5ms
 ❯ apps/next/e2e/preview-sanity.spec.ts (0 test)
 ❯ apps/next/e2e/production-sanity.spec.ts (0 test)
 ✓ packages/app/features/asset/screens/__tests__/geofence-multi-asset-ui.test.ts (11 tests) 5ms
 ❯ apps/next/e2e/asset-features.spec.ts (0 test)
 ✓ packages/app/features/asset/api/__tests__/geofence-team-id-wiring.test.ts (7 tests) 4ms
 ✓ packages/app/features/asset/hooks/__tests__/telemetry-cookie-auth.test.ts (5 tests) 10ms
 ✓ packages/app/features/asset/screens/__tests__/geofence-drawing-no-asset-coupling.test.ts (7 tests) 5ms
 ✓ packages/app/features/asset/screens/__tests__/asset-tracking-location-shape.test.ts (4 tests) 4ms
 ✓ packages/app/features/asset/screens/__tests__/asset-alerts-real-query.test.ts (11 tests) 6ms
 ✓ packages/app/features/asset/api/__tests__/assets-team-id-wiring.test.ts (6 tests) 5ms
 ❯ apps/next/__tests__/server-boot.test.ts (1 test | 1 failed) 3719ms
   × apps/next/dist/server.js loads without ESM/CJS import errors 3718ms
     → server failed to print "Ready on …" within 10s. output:
  Suggestion: If you intended to restart next dev, terminate the other process, and then try again.
(node:1369) [MODULE_TYPELESS_PACKAGE_JSON] Warning: Module type of file:///workspace/source/apps/next/dist/server.js is not specified and it doesn't parse as CommonJS.
Reparsing as ES module because module syntax was detected. This incurs a performance overhead.
To eliminate this warning, add "type": "module" to /workspace/source/apps/next/package.json.
(Use `node --trace-warnings ...` to show where the warning was created)
⨯ Unable to acquire lock at /workspace/source/apps/next/.next/dev/lock, is another instance of next dev running?

[exit 1]: expected false to be true // Object.is equality
 ❯ apps/next/__tests__/ssr-pages.test.ts (9 tests | 9 skipped) 18111ms
 ✓ apps/next/__tests__/ws-cookie-auth.test.ts (3 tests) 3ms
 ❯ apps/next/e2e/asset-rename-sanity.spec.ts (0 test)
 ✓ packages/app/features/asset/api/__tests__/state-enum-types.test.ts (4 tests) 4ms
 ❯ apps/next/e2e/test-filter-modal.spec.ts (0 test)
 ❯ apps/next/e2e/debug-asset-types.spec.ts (0 test)
 ❯ apps/next/e2e/debug-asset-types2.spec.ts (0 test)
 ❯ apps/next/e2e/debug-operations.spec.ts (0 test)
 ❯ apps/next/e2e/debug-login.spec.ts (0 test)
 ❯ apps/next/e2e/debug-login-attempt.spec.ts (0 test)
 ❯ apps/next/__tests__/build.test.ts (1 test | 1 failed) 40531ms
   × Next.js build completes 40530ms
     → expected 'API package built\n[baseline-browser-…' to contain '/vehicles/[id]/settings'
stdout | apps/next/__tests__/build.test.ts
Process already terminated or cannot be killed.

 ❯ apps/next/__tests__/dev.test.ts (1 test | 1 failed) 60006ms
   × Next.js dev server starts 60005ms
     → Test timed out in 60000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".

⎯⎯⎯⎯⎯⎯ Failed Suites 24 ⎯⎯⎯⎯⎯⎯

 FAIL  apps/next/__tests__/ssr-pages.test.ts > SSR page rendering
Error: Server not ready after 30 attempts
 ❯ ClientRequest.<anonymous> apps/next/__tests__/ssr-pages.test.ts:83:18
     81|         req.destroy()
     82|         if (attempts >= maxAttempts) {
     83|           reject(new Error(`Server not ready after ${maxAttempts} atte…
       |                  ^
     84|         } else {
     85|           setTimeout(check, 1000)

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/59]⎯

 FAIL  apps/next/e2e/asset-features.spec.ts [ apps/next/e2e/asset-features.spec.ts ]
Error: Playwright Test did not expect test.describe() to be called here.
Most common reasons include:
- You are calling test.describe() in a configuration file.
- You are calling test.describe() in a file that is imported by the configuration file.
- You have two different versions of @playwright/test. This usually happens
  when one of the dependencies in your package.json depends on @playwright/test.
 ❯ TestTypeImpl._currentSuite node_modules/playwright/lib/common/testType.js:75:13
 ❯ TestTypeImpl._describe node_modules/playwright/lib/common/testType.js:115:24
 ❯ Function.describe node_modules/playwright/lib/transform/transform.js:282:12
 ❯ apps/next/e2e/asset-features.spec.ts:24:6
     22| }
     23| 
     24| test.describe('Asset features E2E', () => {
       |      ^
     25|   test.beforeEach(async ({ page }) => {
     26|     await login(page)

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[2/59]⎯

 FAIL  apps/next/e2e/asset-rename-sanity.spec.ts [ apps/next/e2e/asset-rename-sanity.spec.ts ]
Error: Playwright Test did not expect test.describe() to be called here.
Most common reasons include:
- You are calling test.describe() in a configuration file.
- You are calling test.describe() in a file that is imported by the configuration file.
- You have two different versions of @playwright/test. This usually happens
  when one of the dependencies in your package.json depends on @playwright/test.
 ❯ TestTypeImpl._currentSuite node_modules/playwright/lib/common/testType.js:75:13
 ❯ TestTypeImpl._describe node_modules/playwright/lib/common/testType.js:115:24
 ❯ Function.describe node_modules/playwright/lib/transform/transform.js:282:12
 ❯ apps/next/e2e/asset-rename-sanity.spec.ts:5:6
      3| const BASE = 'http://localhost:3001'
      4| 
      5| test.describe('Asset rename sanity checks', () => {
       |      ^
      6|   test('login page loads without vehicle/fleet text', async ({ page })…
      7|     await page.goto(`${BASE}/login`)

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[3/59]⎯

 FAIL  apps/next/e2e/debug-asset-types.spec.ts [ apps/next/e2e/debug-asset-types.spec.ts ]
Error: Playwright Test did not expect test() to be called here.
Most common reasons include:
- You are calling test() in a configuration file.
- You are calling test() in a file that is imported by the configuration file.
- You have two different versions of @playwright/test. This usually happens
  when one of the dependencies in your package.json depends on @playwright/test.
 ❯ TestTypeImpl._currentSuite node_modules/playwright/lib/common/testType.js:75:13
 ❯ TestTypeImpl._createTest node_modules/playwright/lib/common/testType.js:88:24
 ❯ Module.<anonymous> node_modules/playwright/lib/transform/transform.js:282:12
 ❯ apps/next/e2e/debug-asset-types.spec.ts:2:1
      1| import { test } from '@playwright/test'
      2| test('debug asset types page', async ({ page }) => {
       | ^
      3|   test.setTimeout(60000)
      4|   const errors: string[] = []

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[4/59]⎯

 FAIL  apps/next/e2e/debug-asset-types2.spec.ts [ apps/next/e2e/debug-asset-types2.spec.ts ]
Error: Playwright Test did not expect test() to be called here.
Most common reasons include:
- You are calling test() in a configuration file.
- You are calling test() in a file that is imported by the configuration file.
- You have two different versions of @playwright/test. This usually happens
  when one of the dependencies in your package.json depends on @playwright/test.
 ❯ TestTypeImpl._currentSuite node_modules/playwright/lib/common/testType.js:75:13
 ❯ TestTypeImpl._createTest node_modules/playwright/lib/common/testType.js:88:24
 ❯ Module.<anonymous> node_modules/playwright/lib/transform/transform.js:282:12
 ❯ apps/next/e2e/debug-asset-types2.spec.ts:2:1
      1| import { test } from '@playwright/test'
      2| test('debug asset types network', async ({ page }) => {
       | ^
      3|   test.setTimeout(60000)
      4|   const responses: string[] = []

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[5/59]⎯

 FAIL  apps/next/e2e/debug-login-attempt.spec.ts [ apps/next/e2e/debug-login-attempt.spec.ts ]
Error: Playwright Test did not expect test() to be called here.
Most common reasons include:
- You are calling test() in a configuration file.
- You are calling test() in a file that is imported by the configuration file.
- You have two different versions of @playwright/test. This usually happens
  when one of the dependencies in your package.json depends on @playwright/test.
 ❯ TestTypeImpl._currentSuite node_modules/playwright/lib/common/testType.js:75:13
 ❯ TestTypeImpl._createTest node_modules/playwright/lib/common/testType.js:88:24
 ❯ Module.<anonymous> node_modules/playwright/lib/transform/transform.js:282:12
 ❯ apps/next/e2e/debug-login-attempt.spec.ts:2:1
      1| import { test } from '@playwright/test'
      2| test('debug login attempt', async ({ page }) => {
       | ^
      3|   await page.goto('https://flash-pr3.voltcred.com/login', { waitUntil:…
      4|   await page.waitForTimeout(2000)

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[6/59]⎯

 FAIL  apps/next/e2e/debug-login.spec.ts [ apps/next/e2e/debug-login.spec.ts ]
Error: Playwright Test did not expect test() to be called here.
Most common reasons include:
- You are calling test() in a configuration file.
- You are calling test() in a file that is imported by the configuration file.
- You have two different versions of @playwright/test. This usually happens
  when one of the dependencies in your package.json depends on @playwright/test.
 ❯ TestTypeImpl._currentSuite node_modules/playwright/lib/common/testType.js:75:13
 ❯ TestTypeImpl._createTest node_modules/playwright/lib/common/testType.js:88:24
 ❯ Module.<anonymous> node_modules/playwright/lib/transform/transform.js:282:12
 ❯ apps/next/e2e/debug-login.spec.ts:2:1
      1| import { test } from '@playwright/test'
      2| test('debug login page', async ({ page }) => {
       | ^
      3|   await page.goto('https://flash-pr3.voltcred.com/login', { waitUntil:…
      4|   await page.waitForTimeout(5000)

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[7/59]⎯

 FAIL  apps/next/e2e/debug-operations.spec.ts [ apps/next/e2e/debug-operations.spec.ts ]
Error: Playwright Test did not expect test() to be called here.
Most common reasons include:
- You are calling test() in a configuration file.
- You are calling test() in a file that is imported by the configuration file.
- You have two different versions of @playwright/test. This usually happens
  when one of the dependencies in your package.json depends on @playwright/test.
 ❯ TestTypeImpl._currentSuite node_modules/playwright/lib/common/testType.js:75:13
 ❯ TestTypeImpl._createTest node_modules/playwright/lib/common/testType.js:88:24
 ❯ Module.<anonymous> node_modules/playwright/lib/transform/transform.js:282:12
 ❯ apps/next/e2e/debug-operations.spec.ts:3:1
      1| import { test } from '@playwright/test'
      2| 
      3| test('debug operations page console errors', async ({ page }) => {
       | ^
      4|   test.setTimeout(60000)
      5| 

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[8/59]⎯

 FAIL  apps/next/e2e/preview-sanity.spec.ts [ apps/next/e2e/preview-sanity.spec.ts ]
Error: Playwright Test did not expect test.describe() to be called here.
Most common reasons include:
- You are calling test.describe() in a configuration file.
- You are calling test.describe() in a file that is imported by the configuration file.
- You have two different versions of @playwright/test. This usually happens
  when one of the dependencies in your package.json depends on @playwright/test.
 ❯ TestTypeImpl._currentSuite node_modules/playwright/lib/common/testType.js:75:13
 ❯ TestTypeImpl._describe node_modules/playwright/lib/common/testType.js:115:24
 ❯ Function.describe node_modules/playwright/lib/transform/transform.js:282:12
 ❯ apps/next/e2e/preview-sanity.spec.ts:17:6
     15| }
     16| 
     17| test.describe('Preview E2E — Asset Rename Verification', () => {
       |      ^
     18|   test.setTimeout(60000)
     19| 

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[9/59]⎯

 FAIL  apps/next/e2e/production-sanity.spec.ts [ apps/next/e2e/production-sanity.spec.ts ]
Error: Playwright Test did not expect test.describe() to be called here.
Most common reasons include:
- You are calling test.describe() in a configuration file.
- You are calling test.describe() in a file that is imported by the configuration file.
- You have two different versions of @playwright/test. This usually happens
  when one of the dependencies in your package.json depends on @playwright/test.
 ❯ TestTypeImpl._currentSuite node_modules/playwright/lib/common/testType.js:75:13
 ❯ TestTypeImpl._describe node_modules/playwright/lib/common/testType.js:115:24
 ❯ Function.describe node_modules/playwright/lib/transform/transform.js:282:12
 ❯ apps/next/e2e/production-sanity.spec.ts:14:6
     12| }
     13| 
     14| test.describe('Production sanity after rename', () => {
       |      ^
     15|   test.setTimeout(90000)
     16| 

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[10/59]⎯

 FAIL  apps/next/e2e/test-filter-modal.spec.ts [ apps/next/e2e/test-filter-modal.spec.ts ]
Error: Playwright Test did not expect test() to be called here.
Most common reasons include:
- You are calling test() in a configuration file.
- You are calling test() in a file that is imported by the configuration file.
- You have two different versions of @playwright/test. This usually happens
  when one of the dependencies in your package.json depends on @playwright/test.
 ❯ TestTypeImpl._currentSuite node_modules/playwright/lib/common/testType.js:75:13
 ❯ TestTypeImpl._createTest node_modules/playwright/lib/common/testType.js:88:24
 ❯ Module.<anonymous> node_modules/playwright/lib/transform/transform.js:282:12
 ❯ apps/next/e2e/test-filter-modal.spec.ts:3:1
      1| import { test, expect } from '@playwright/test'
      2| 
      3| test('filter modal opens and shows content on MORE click', async ({ pa…
       | ^
      4|   test.setTimeout(90000)
      5| 

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[11/59]⎯

 FAIL  apps/next/__tests__/components/documents-client.test.tsx [ apps/next/__tests__/components/documents-client.test.tsx ]
Error: Failed to resolve import "../../app/(protected)/vehicles/documents/documents-client" from "apps/next/__tests__/components/documents-client.test.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: /workspace/source/apps/next/__tests__/components/documents-client.test.tsx:49:38
  47 |  const __vi_import_0__ = await import('react')
  48 |  const __vi_import_1__ = await import('@testing-library/react')
  49 |  const __vi_import_2__ = await import('../../app/(protected)/vehicles/documents/documents-client')
     |                                       ^
  50 |  
  51 |  import { describe, test, expect, vi, afterEach } from "vitest";
 ❯ TransformPluginContext._formatError node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49258:41
 ❯ TransformPluginContext.error node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49253:16
 ❯ normalizeUrl node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64306:23
 ❯ node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64438:39
 ❯ TransformPluginContext.transform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64365:7
 ❯ PluginContainer.transform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49099:18
 ❯ loadAndTransform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:51977:27

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[12/59]⎯

 FAIL  apps/next/__tests__/components/events-client.test.tsx [ apps/next/__tests__/components/events-client.test.tsx ]
Error: Failed to resolve import "../../app/(protected)/vehicles/[id]/events/events-client" from "apps/next/__tests__/components/events-client.test.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: /workspace/source/apps/next/__tests__/components/events-client.test.tsx:44:38
  42 |  const __vi_import_0__ = await import('react')
  43 |  const __vi_import_1__ = await import('@testing-library/react')
  44 |  const __vi_import_2__ = await import('../../app/(protected)/vehicles/[id]/events/events-client')
     |                                       ^
  45 |  
  46 |  import { describe, test, expect, vi, beforeEach, afterEach } from "vitest";
 ❯ TransformPluginContext._formatError node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49258:41
 ❯ TransformPluginContext.error node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49253:16
 ❯ normalizeUrl node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64306:23
 ❯ node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64438:39
 ❯ TransformPluginContext.transform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64365:7
 ❯ PluginContainer.transform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49099:18
 ❯ loadAndTransform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:51977:27

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[13/59]⎯

 FAIL  apps/next/__tests__/components/maintenance-client.test.tsx [ apps/next/__tests__/components/maintenance-client.test.tsx ]
Error: Failed to resolve import "../../app/(protected)/vehicles/maintenance/maintenance-client" from "apps/next/__tests__/components/maintenance-client.test.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: /workspace/source/apps/next/__tests__/components/maintenance-client.test.tsx:49:38
  47 |  const __vi_import_0__ = await import('react')
  48 |  const __vi_import_1__ = await import('@testing-library/react')
  49 |  const __vi_import_2__ = await import('../../app/(protected)/vehicles/maintenance/maintenance-client')
     |                                       ^
  50 |  
  51 |  import { describe, test, expect, vi, afterEach } from "vitest";
 ❯ TransformPluginContext._formatError node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49258:41
 ❯ TransformPluginContext.error node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49253:16
 ❯ normalizeUrl node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64306:23
 ❯ node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64438:39
 ❯ TransformPluginContext.transform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64365:7
 ❯ PluginContainer.transform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49099:18
 ❯ loadAndTransform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:51977:27

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[14/59]⎯

 FAIL  apps/next/__tests__/components/replay-page.test.tsx [ apps/next/__tests__/components/replay-page.test.tsx ]
Error: Failed to resolve import "../../app/(protected)/vehicles/[id]/replay/replay-client" from "apps/next/__tests__/components/replay-page.test.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: /workspace/source/apps/next/__tests__/components/replay-page.test.tsx:88:38
  86 |  const __vi_import_0__ = await import('react')
  87 |  const __vi_import_1__ = await import('@testing-library/react')
  88 |  const __vi_import_2__ = await import('../../app/(protected)/vehicles/[id]/replay/replay-client')
     |                                       ^
  89 |  
  90 |  import { describe, test, expect, vi, beforeEach, afterEach } from "vitest";
 ❯ TransformPluginContext._formatError node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49258:41
 ❯ TransformPluginContext.error node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49253:16
 ❯ normalizeUrl node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64306:23
 ❯ node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64438:39
 ❯ TransformPluginContext.transform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64365:7
 ❯ PluginContainer.transform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49099:18
 ❯ loadAndTransform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:51977:27

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[15/59]⎯

 FAIL  apps/next/__tests__/components/settings-client.test.tsx [ apps/next/__tests__/components/settings-client.test.tsx ]
Error: Failed to resolve import "../../app/(protected)/vehicles/[id]/settings/settings-client" from "apps/next/__tests__/components/settings-client.test.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: /workspace/source/apps/next/__tests__/components/settings-client.test.tsx:48:38
  46 |  const __vi_import_0__ = await import('react')
  47 |  const __vi_import_1__ = await import('@testing-library/react')
  48 |  const __vi_import_2__ = await import('../../app/(protected)/vehicles/[id]/settings/settings-client')
     |                                       ^
  49 |  
  50 |  import { describe, test, expect, vi, beforeEach, afterEach } from "vitest";
 ❯ TransformPluginContext._formatError node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49258:41
 ❯ TransformPluginContext.error node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49253:16
 ❯ normalizeUrl node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64306:23
 ❯ node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64438:39
 ❯ TransformPluginContext.transform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64365:7
 ❯ PluginContainer.transform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49099:18
 ❯ loadAndTransform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:51977:27

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[16/59]⎯

 FAIL  apps/next/__tests__/components/vehicle-assignment-screen.test.tsx [ apps/next/__tests__/components/vehicle-assignment-screen.test.tsx ]
Error: Failed to resolve import "app/features/asset/screens/VehicleAssignmentScreen" from "apps/next/__tests__/components/vehicle-assignment-screen.test.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: /workspace/source/apps/next/__tests__/components/vehicle-assignment-screen.test.tsx:93:38
  91 |  const __vi_import_0__ = await import('react')
  92 |  const __vi_import_1__ = await import('@testing-library/react')
  93 |  const __vi_import_2__ = await import('app/features/asset/screens/VehicleAssignmentScreen')
     |                                       ^
  94 |  
  95 |  import { describe, test, expect, vi, afterEach } from "vitest";
 ❯ TransformPluginContext._formatError node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49258:41
 ❯ TransformPluginContext.error node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49253:16
 ❯ normalizeUrl node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64306:23
 ❯ node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64438:39
 ❯ TransformPluginContext.transform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64365:7
 ❯ PluginContainer.transform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49099:18
 ❯ loadAndTransform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:51977:27

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[17/59]⎯

 FAIL  apps/next/__tests__/components/vehicle-iot-settings-screen.test.tsx [ apps/next/__tests__/components/vehicle-iot-settings-screen.test.tsx ]
Error: Failed to resolve import "app/features/asset/screens/VehicleIoTSettingsScreen" from "apps/next/__tests__/components/vehicle-iot-settings-screen.test.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: /workspace/source/apps/next/__tests__/components/vehicle-iot-settings-screen.test.tsx:71:38
  69 |  const __vi_import_0__ = await import('react')
  70 |  const __vi_import_1__ = await import('@testing-library/react')
  71 |  const __vi_import_2__ = await import('app/features/asset/screens/VehicleIoTSettingsScreen')
     |                                       ^
  72 |  
  73 |  import { describe, test, expect, vi, afterEach } from "vitest";
 ❯ TransformPluginContext._formatError node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49258:41
 ❯ TransformPluginContext.error node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49253:16
 ❯ normalizeUrl node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64306:23
 ❯ node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64438:39
 ❯ TransformPluginContext.transform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64365:7
 ❯ PluginContainer.transform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49099:18
 ❯ loadAndTransform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:51977:27

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[18/59]⎯

 FAIL  apps/next/__tests__/components/vehicle-models-screen.test.tsx [ apps/next/__tests__/components/vehicle-models-screen.test.tsx ]
Error: Failed to resolve import "app/features/asset/screens/VehicleModelsScreen" from "apps/next/__tests__/components/vehicle-models-screen.test.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: /workspace/source/apps/next/__tests__/components/vehicle-models-screen.test.tsx:87:38
  85 |  const __vi_import_0__ = await import('react')
  86 |  const __vi_import_1__ = await import('@testing-library/react')
  87 |  const __vi_import_2__ = await import('app/features/asset/screens/VehicleModelsScreen')
     |                                       ^
  88 |  
  89 |  import { describe, test, expect, vi, afterEach } from "vitest";
 ❯ TransformPluginContext._formatError node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49258:41
 ❯ TransformPluginContext.error node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49253:16
 ❯ normalizeUrl node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64306:23
 ❯ node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64438:39
 ❯ TransformPluginContext.transform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64365:7
 ❯ PluginContainer.transform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49099:18
 ❯ loadAndTransform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:51977:27

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[19/59]⎯

 FAIL  apps/next/__tests__/components/vehicle-tracking-screen.test.tsx [ apps/next/__tests__/components/vehicle-tracking-screen.test.tsx ]
Error: Failed to resolve import "app/features/asset/screens/VehicleTrackingScreen" from "apps/next/__tests__/components/vehicle-tracking-screen.test.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: /workspace/source/apps/next/__tests__/components/vehicle-tracking-screen.test.tsx:77:38
  75 |  const __vi_import_0__ = await import('react')
  76 |  const __vi_import_1__ = await import('@testing-library/react')
  77 |  const __vi_import_2__ = await import('app/features/asset/screens/VehicleTrackingScreen')
     |                                       ^
  78 |  
  79 |  import { describe, test, expect, vi, afterEach } from "vitest";
 ❯ TransformPluginContext._formatError node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49258:41
 ❯ TransformPluginContext.error node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49253:16
 ❯ normalizeUrl node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64306:23
 ❯ node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64438:39
 ❯ TransformPluginContext.transform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64365:7
 ❯ PluginContainer.transform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49099:18
 ❯ loadAndTransform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:51977:27

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[20/59]⎯

 FAIL  apps/next/__tests__/components/vehicles-_client.test.tsx [ apps/next/__tests__/components/vehicles-_client.test.tsx ]
Error: Failed to resolve import "../../app/(protected)/vehicles/_client" from "apps/next/__tests__/components/vehicles-_client.test.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: /workspace/source/apps/next/__tests__/components/vehicles-_client.test.tsx:22:38
  20 |  const __vi_import_0__ = await import('react')
  21 |  const __vi_import_1__ = await import('@testing-library/react')
  22 |  const __vi_import_2__ = await import('../../app/(protected)/vehicles/_client')
     |                                       ^
  23 |  
  24 |  import { describe, test, expect, vi, afterEach } from "vitest";
 ❯ TransformPluginContext._formatError node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49258:41
 ❯ TransformPluginContext.error node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49253:16
 ❯ normalizeUrl node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64306:23
 ❯ node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64438:39
 ❯ TransformPluginContext.transform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64365:7
 ❯ PluginContainer.transform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49099:18
 ❯ loadAndTransform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:51977:27

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[21/59]⎯

 FAIL  apps/next/__tests__/components/vehicles-client.test.tsx [ apps/next/__tests__/components/vehicles-client.test.tsx ]
Error: Failed to resolve import "../../app/(protected)/vehicles/vehicles-client" from "apps/next/__tests__/components/vehicles-client.test.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: /workspace/source/apps/next/__tests__/components/vehicles-client.test.tsx:29:38
  27 |  const __vi_import_0__ = await import('react')
  28 |  const __vi_import_1__ = await import('@testing-library/react')
  29 |  const __vi_import_2__ = await import('../../app/(protected)/vehicles/vehicles-client')
     |                                       ^
  30 |  
  31 |  import { describe, test, expect, vi, afterEach } from "vitest";
 ❯ TransformPluginContext._formatError node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49258:41
 ❯ TransformPluginContext.error node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49253:16
 ❯ normalizeUrl node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64306:23
 ❯ node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64438:39
 ❯ TransformPluginContext.transform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64365:7
 ❯ PluginContainer.transform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49099:18
 ❯ loadAndTransform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:51977:27

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[22/59]⎯

 FAIL  apps/next/__tests__/components/voltcred-vehicle-detail-screen.test.tsx [ apps/next/__tests__/components/voltcred-vehicle-detail-screen.test.tsx ]
Error: Failed to resolve import "app/features/asset/screens/VoltCredVehicleDetailScreen" from "apps/next/__tests__/components/voltcred-vehicle-detail-screen.test.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: /workspace/source/apps/next/__tests__/components/voltcred-vehicle-detail-screen.test.tsx:72:38
  70 |  const __vi_import_0__ = await import('react')
  71 |  const __vi_import_1__ = await import('@testing-library/react')
  72 |  const __vi_import_2__ = await import('app/features/asset/screens/VoltCredVehicleDetailScreen')
     |                                       ^
  73 |  
  74 |  import { describe, test, expect, vi, beforeEach, afterEach } from "vitest";
 ❯ TransformPluginContext._formatError node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49258:41
 ❯ TransformPluginContext.error node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49253:16
 ❯ normalizeUrl node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64306:23
 ❯ node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64438:39
 ❯ TransformPluginContext.transform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64365:7
 ❯ PluginContainer.transform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49099:18
 ❯ loadAndTransform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:51977:27

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[23/59]⎯

 FAIL  apps/next/__tests__/components/voltcred-vehicle-list-screen.test.tsx [ apps/next/__tests__/components/voltcred-vehicle-list-screen.test.tsx ]
Error: Failed to resolve import "app/features/asset/screens/VoltCredVehicleListScreen" from "apps/next/__tests__/components/voltcred-vehicle-list-screen.test.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: /workspace/source/apps/next/__tests__/components/voltcred-vehicle-list-screen.test.tsx:72:38
  70 |  const __vi_import_0__ = await import('react')
  71 |  const __vi_import_1__ = await import('@testing-library/react')
  72 |  const __vi_import_2__ = await import('app/features/asset/screens/VoltCredVehicleListScreen')
     |                                       ^
  73 |  
  74 |  import { describe, test, expect, vi, beforeEach, afterEach } from "vitest";
 ❯ TransformPluginContext._formatError node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49258:41
 ❯ TransformPluginContext.error node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49253:16
 ❯ normalizeUrl node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64306:23
 ❯ node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64438:39
 ❯ TransformPluginContext.transform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:64365:7
 ❯ PluginContainer.transform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:49099:18
 ❯ loadAndTransform node_modules/vitest/node_modules/vite/dist/node/chunks/dep-D_zLpgQd.js:51977:27

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[24/59]⎯

⎯⎯⎯⎯⎯⎯ Failed Tests 35 ⎯⎯⎯⎯⎯⎯⎯

 FAIL  apps/next/__tests__/build.test.ts > Next.js build completes
AssertionError: expected 'API package built\n[baseline-browser-…' to contain '/vehicles/[id]/settings'

- Expected
+ Received

- /vehicles/[id]/settings
+ API package built
+ [baseline-browser-mapping] The data in this module is over two months old.  To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
+ built @my/config in 605 ms
+ [baseline-browser-mapping] The data in this module is over two months old.  To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
+ built @my/ui in 1007 ms
+ Done in 6s 202ms
+ ▲ Next.js 16.1.1 (Turbopack)
+ - Environments: .env
+ - Experiments (use with caution):
+   ✓ scrollRestoration
+
+ ⚠ The "middleware" file convention is deprecated. Please use "proxy" instead. Learn more: https://nextjs.org/docs/messages/middleware-to-proxy
+   Creating an optimized production build ...
+ ✓ Compiled successfully in 26.6s
+   Skipping validation of types
+   Collecting page data using 3 workers ...
+   Generating static pages using 3 workers (0/29) ...
+   Generating static pages using 3 workers (7/29) 
+   Generating static pages using 3 workers (14/29) 
+   Generating static pages using 3 workers (21/29) 
+ Failed to resolve default team: Error: Dynamic server usage: Route / couldn't be rendered statically because it used `cookies`. See more info here: https://nextjs.org/docs/messages/dynamic-server-error
+     at e (.next/server/chunks/ssr/_40f3cae4._.js:25:7164)
+     at <unknown> (.next/server/chunks/ssr/_40f3cae4._.js:13:71692)
+     at <unknown> (.next/server/chunks/ssr/_40f3cae4._.js:18:23)
+     at query (.next/server/chunks/ssr/_40f3cae4._.js:35:28)
+     at f (.next/server/chunks/ssr/[root-of-the-server]__41d8655b._.js:7:66) {
+   description: "Route / couldn't be rendered statically because it used `cookies`. See more info here: https://nextjs.org/docs/messages/dynamic-server-error",
+   digest: 'DYNAMIC_SERVER_USAGE'
+ }
+ ✓ Generating static pages using 3 workers (29/29) in 456.6ms
+   Finalizing page optimization ...
+
+ Route (app)
+ ┌ ƒ /
+ ├ ƒ /_not-found
+ ├ ƒ /[team_id]
+ ├ ƒ /[team_id]/assets
+ ├ ƒ /[team_id]/assets/[id]
+ ├ ƒ /[team_id]/assets/[id]/events
+ ├ ƒ /[team_id]/assets/[id]/geofence
+ ├ ƒ /[team_id]/assets/[id]/geofence/[geofenceId]
+ ├ ƒ /[team_id]/assets/[id]/replay
+ ├ ƒ /[team_id]/assets/[id]/settings
+ ├ ƒ /[team_id]/assets/documents
+ ├ ƒ /[team_id]/assets/maintenance
+ ├ ƒ /[team_id]/assets/models
+ ├ ƒ /[team_id]/assets/types
+ ├ ƒ /[team_id]/reports
+ ├ ƒ /api/health
+ ├ ƒ /auth/google/callback
+ ├ ƒ /customer
+ ├ ƒ /customer/assets
+ ├ ƒ /customer/commands
+ ├ ƒ /customer/profile
+ ├ ƒ /customer/track
+ ├ ƒ /driver-management
+ ├ ƒ /forgot-password
+ ├ ƒ /geofences
+ ├ ƒ /geofences/new
+ ├ ƒ /hubs
+ ├ ƒ /login
+ ├ ƒ /members
+ ├ ƒ /no-team
+ ├ ƒ /operations
+ ├ ƒ /operations/challans
+ ├ ƒ /operations/gatepasses
+ ├ ƒ /operations/trips
+ ├ ƒ /operations/trips/[id]
+ ├ ƒ /operations/violations
+ ├ ƒ /routes
+ ├ ƒ /signup
+ ├ ƒ /team
+ ├ ƒ /team-management
+ ├ ƒ /teams
+ ├ ƒ /teams/[id]
+ ├ ƒ /teams/new
+ └ ƒ /user/[id]
+
+
+ ƒ Proxy (Middleware)
+
+ ƒ  (Dynamic)  server-rendered on demand
+
+

 ❯ apps/next/__tests__/build.test.ts:56:20
     54| 
     55|     // Check for important routes that should stay present
     56|     expect(result).toContain('/vehicles/[id]/settings')
       |                    ^
     57|     expect(result).toContain('/vehicles/[id]/geofence')
     58|     expect(result).toContain('/vehicles/[id]/geofence/[geofenceId]')

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[25/59]⎯

 FAIL  apps/next/__tests__/dev.test.ts > Next.js dev server starts
Error: Test timed out in 60000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[26/59]⎯

 FAIL  apps/next/__tests__/server-boot.test.ts > apps/next/dist/server.js loads without ESM/CJS import errors
AssertionError: server failed to print "Ready on …" within 10s. output:
  Suggestion: If you intended to restart next dev, terminate the other process, and then try again.
(node:1369) [MODULE_TYPELESS_PACKAGE_JSON] Warning: Module type of file:///workspace/source/apps/next/dist/server.js is not specified and it doesn't parse as CommonJS.
Reparsing as ES module because module syntax was detected. This incurs a performance overhead.
To eliminate this warning, add "type": "module" to /workspace/source/apps/next/package.json.
(Use `node --trace-warnings ...` to show where the warning was created)
⨯ Unable to acquire lock at /workspace/source/apps/next/.next/dev/lock, is another instance of next dev running?

[exit 1]: expected false to be true // Object.is equality

- Expected
+ Received

- true
+ false

 ❯ apps/next/__tests__/server-boot.test.ts:73:102
     71| 
     72|   expect(result.output).not.toMatch(/SyntaxError|Named export.*not fou…
     73|   expect(result.booted, `server failed to print "Ready on …" within 10…
       |                                                                                                      ^
     74| }, 30_000)
     75| 

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[27/59]⎯

 FAIL  apps/next/__tests__/components/driver-performance-screen.test.tsx > DriverPerformanceScreen > shows fleet average comparison
AssertionError: expected false to be true // Object.is equality

- Expected
+ Received

- true
+ false

 ❯ apps/next/__tests__/components/driver-performance-screen.test.tsx:108:52
    106|   test('shows fleet average comparison', () => {
    107|     const { container } = render(React.createElement(DriverPerformance…
    108|     expect(hasText(container, 'vs Fleet Average')).toBe(true)
       |                                                    ^
    109|   })
    110| 

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[28/59]⎯

 FAIL  apps/next/__tests__/components/error-pages.test.tsx > 404 Not Found Page > has quick navigation links
AssertionError: expected false to be true // Object.is equality

- Expected
+ Received

- true
+ false

 ❯ apps/next/__tests__/components/error-pages.test.tsx:80:44
     78|     const { container } = render(React.createElement(NotFound))
     79|     expect(hasText(container, 'Dashboard')).toBe(true)
     80|     expect(hasText(container, 'Vehicles')).toBe(true)
       |                                            ^
     81|   })
     82| 

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[29/59]⎯

 FAIL  apps/next/__tests__/components/error-pages.test.tsx > 403 Forbidden Page > shows role subtitles
AssertionError: expected false to be true // Object.is equality

- Expected
+ Received

- true
+ false

 ❯ apps/next/__tests__/components/error-pages.test.tsx:221:51
    219|     const { default: ForbiddenPage } = await import('../../app/(protec…
    220|     const { container } = render(React.createElement(ForbiddenPage))
    221|     expect(hasText(container, 'Fleet Operators')).toBe(true)
       |                                                   ^
    222|     expect(hasText(container, 'Fleet Manager')).toBe(true)
    223|   })

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[30/59]⎯

 FAIL  apps/next/__tests__/components/fleet-live-tracking-screen.test.tsx > LiveTrackingScreen > renders without crashing
 FAIL  apps/next/__tests__/components/fleet-live-tracking-screen.test.tsx > LiveTrackingScreen > shows Vehicles header
 FAIL  apps/next/__tests__/components/fleet-live-tracking-screen.test.tsx > LiveTrackingScreen > shows LIVE badge
 FAIL  apps/next/__tests__/components/fleet-live-tracking-screen.test.tsx > LiveTrackingScreen > renders vehicle registrations
 FAIL  apps/next/__tests__/components/fleet-live-tracking-screen.test.tsx > LiveTrackingScreen > shows status counts
 FAIL  apps/next/__tests__/components/fleet-live-tracking-screen.test.tsx > LiveTrackingScreen > renders map wrapper
 FAIL  apps/next/__tests__/components/fleet-live-tracking-screen.test.tsx > LiveTrackingScreen > shows no vehicles message when filtered empty
 FAIL  apps/next/__tests__/components/fleet-live-tracking-screen.test.tsx > LiveTrackingScreen > shows speed for vehicles
TypeError: Cannot read properties of undefined (reading 'length')
 ❯ packages/app/features/asset/screens/LiveTrackingScreen.tsx:132:21
    130|   const stats = useMemo(
    131|     () => ({
    132|       total: assets.length,
       |                     ^
    133|       moving: assets.filter((v) => v.status === 'moving').length,
    134|       idle: assets.filter((v) => v.status === 'idle').length,
 ❯ mountMemo node_modules/react-dom/cjs/react-dom-client.development.js:6603:23
 ❯ Object.useMemo node_modules/react-dom/cjs/react-dom-client.development.js:22924:18
 ❯ Proxy.process.env.NODE_ENV.exports.useMemo node_modules/react/cjs/react.development.js:1209:34
 ❯ LiveTrackingScreen packages/app/features/asset/screens/LiveTrackingScreen.tsx:130:17
 ❯ Object.react-stack-bottom-frame node_modules/react-dom/cjs/react-dom-client.development.js:23863:20
 ❯ renderWithHooks node_modules/react-dom/cjs/react-dom-client.development.js:5529:22
 ❯ updateFunctionComponent node_modules/react-dom/cjs/react-dom-client.development.js:8897:19
 ❯ beginWork node_modules/react-dom/cjs/react-dom-client.development.js:10522:18
 ❯ runWithFiberInDEV node_modules/react-dom/cjs/react-dom-client.development.js:1522:13

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[31/59]⎯

 FAIL  apps/next/__tests__/components/fleet-operations-screen.test.tsx > OperationsScreen > shows Fleet Operations header
AssertionError: expected false to be true // Object.is equality

- Expected
+ Received

- true
+ false

 ❯ apps/next/__tests__/components/fleet-operations-screen.test.tsx:102:52
    100|   test('shows Fleet Operations header', () => {
    101|     const { container } = render(React.createElement(OperationsScreen))
    102|     expect(hasText(container, 'Fleet Operations')).toBe(true)
       |                                                    ^
    103|   })
    104| 

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[32/59]⎯

 FAIL  apps/next/__tests__/components/geofence-drawing-screen.test.tsx > GeofenceDrawingScreen > shows Vehicle Info section
AssertionError: expected false to be true // Object.is equality

- Expected
+ Received

- true
+ false

 ❯ apps/next/__tests__/components/geofence-drawing-screen.test.tsx:141:48
    139|       })
    140|     )
    141|     expect(hasText(container, 'Vehicle Info')).toBe(true)
       |                                                ^
    142|     expect(hasText(container, 'DL-01-AB-1234')).toBe(true)
    143|   })

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[33/59]⎯

 FAIL  apps/next/__tests__/components/geofences-page.test.tsx > GeofencesPage component > renders without crashing
 FAIL  apps/next/__tests__/components/geofences-page.test.tsx > GeofencesPage component > shows loading spinner when loading with no data
 FAIL  apps/next/__tests__/components/geofences-page.test.tsx > GeofencesPage component > shows Zone Directory header
 FAIL  apps/next/__tests__/components/geofences-page.test.tsx > GeofencesPage component > renders stat card labels
 FAIL  apps/next/__tests__/components/geofences-page.test.tsx > GeofencesPage component > default active tab shows only enabled geofences
 FAIL  apps/next/__tests__/components/geofences-page.test.tsx > GeofencesPage component > clicking All tab shows all geofences
 FAIL  apps/next/__tests__/components/geofences-page.test.tsx > GeofencesPage component > search filters geofences by name
 FAIL  apps/next/__tests__/components/geofences-page.test.tsx > GeofencesPage component > no search matches shows appropriate message
 FAIL  apps/next/__tests__/components/geofences-page.test.tsx > GeofencesPage component > empty geofences shows no geofences yet message
 FAIL  apps/next/__tests__/components/geofences-page.test.tsx > GeofencesPage component > toggle switch calls updateGeofence
 FAIL  apps/next/__tests__/components/geofences-page.test.tsx > GeofencesPage component > Create Zone button navigates to /vehicles
 FAIL  apps/next/__tests__/components/geofences-page.test.tsx > GeofencesPage component > export button is disabled when no geofences
 FAIL  apps/next/__tests__/components/geofences-page.test.tsx > GeofencesPage component > renders map placeholder
 FAIL  apps/next/__tests__/components/geofences-page.test.tsx > GeofencesPage component > geofence card shows type label for circle with radius
 FAIL  apps/next/__tests__/components/geofences-page.test.tsx > GeofencesPage component > geofence card shows vehicle count
 FAIL  apps/next/__tests__/components/geofences-page.test.tsx > GeofencesPage component > loading with existing data does not show spinner
 FAIL  apps/next/__tests__/components/geofences-page.test.tsx > GeofencesPage component > null data renders empty state
 FAIL  apps/next/__tests__/components/geofences-page.test.tsx > GeofencesPage component > alerts text shows Entry for entry-only geofence
Error: [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"?
If you need to partially mock a module, you can use "importOriginal" helper inside:

vi.mock(import("app/features/asset/api/hooks"), async (importOriginal) => {
  const actual = await importOriginal()
  return {
    ...actual,
    // your mocked methods
  }
})

 ❯ Module.useTeamSelector packages/app/hooks/useTeamSelector.ts:23:36
     21|  */
     22| export function useTeamSelector(currentTeamId?: number) {
     23|   const { data, loading, error } = useAssetTeams()
       |                                    ^
     24| 
     25|   const availableTeams: TeamSelectorTeam[] = useMemo(() => {
 ❯ GeofencesPage apps/next/app/(protected)/geofences/page.tsx:163:30
 ❯ Object.react-stack-bottom-frame node_modules/react-dom/cjs/react-dom-client.development.js:23863:20
 ❯ renderWithHooks node_modules/react-dom/cjs/react-dom-client.development.js:5529:22
 ❯ updateFunctionComponent node_modules/react-dom/cjs/react-dom-client.development.js:8897:19
 ❯ beginWork node_modules/react-dom/cjs/react-dom-client.development.js:10522:18
 ❯ runWithFiberInDEV node_modules/react-dom/cjs/react-dom-client.development.js:1522:13
 ❯ performUnitOfWork node_modules/react-dom/cjs/react-dom-client.development.js:15140:22

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[34/59]⎯

 FAIL  apps/next/__tests__/components/trip-list-screen.test.tsx > TripListScreen > shows Fleet Trips header
AssertionError: expected false to be true // Object.is equality

- Expected
+ Received

- true
+ false

 ❯ apps/next/__tests__/components/trip-list-screen.test.tsx:106:47
    104|   test('shows Fleet Trips header', () => {
    105|     const { container } = render(React.createElement(TripListScreen))
    106|     expect(hasText(container, 'Fleet Trips')).toBe(true)
       |                                               ^
    107|   })
    108| 

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[35/59]⎯

⎯⎯⎯⎯⎯⎯ Unhandled Errors ⎯⎯⎯⎯⎯⎯

Vitest caught 1 unhandled error during the test run.
This might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected.

⎯⎯⎯⎯⎯ Uncaught Exception ⎯⎯⎯⎯⎯
Error: spawn ps ENOENT
 ❯ Process.ChildProcess._handle.onexit node:internal/child_process:285:19
 ❯ onErrorNT node:internal/child_process:483:16
 ❯ processTicksAndRejections node:internal/process/task_queues:89:21

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { errno: -2, code: 'ENOENT', syscall: 'spawn ps', path: 'ps', spawnargs: [ '-o', 'pid', '--no-headers', '--ppid', 1257 ] }
This error originated in "apps/next/__tests__/dev.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "Next.js dev server starts". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

 Test Files  34 failed | 32 passed (66)
      Tests  35 failed | 335 passed | 9 skipped (379)
     Errors  1 error
   Start at  19:19:38
   Duration  78.69s (transform 1.38s, setup 0ms, collect 5.41s, tests 126.63s, environment 29.68s, prepare 4.73s)


Pipeline failed on stage 'from-build-pack' : container 'step-unit-tests'. The execution of the pipeline has stopped.