Logs complete · 66 chunks
[Checkout] Cloning into '/var/lib/open-git/runner-work/33970a0f-4398-4232-bc8e-c1934aaa2c4c'...
[Checkout] Note: switching to 'cb4a0e5e8fe26ab2665572c0b2a3fda7584c7dbd'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:
git switch -c <new-branch-name>
Or undo this operation with:
git switch -
Turn off this advice by setting config variable advice.detachedHead to false
HEAD is now at cb4a0e5 fix(repo): repository shell/tabs/home adjustments
[Install deps and run eslint] Preparing pnpm@9.15.9 for immediate activation...
[Install deps and run eslint] Scope: all 19 workspace projects
[Install deps and run eslint] Lockfile is up to date, resolution step is skipped
[Install deps and run eslint] Progress: resolved 1, reused 0, downloaded 0, added 0
[Install deps and run eslint] Packages: +1196
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[Install deps and run eslint] Progress: resolved 1196, reused 0, downloaded 15, added 0
[Install deps and run eslint] Progress: resolved 1196, reused 0, downloaded 29, added 14
[Install deps and run eslint] Progress: resolved 1196, reused 0, downloaded 43, added 29
[Install deps and run eslint] Progress: resolved 1196, reused 0, downloaded 44, added 29
[Install deps and run eslint] Progress: resolved 1196, reused 0, downloaded 183, added 173
[Install deps and run eslint] Progress: resolved 1196, reused 0, downloaded 315, added 303
[Install deps and run eslint] Progress: resolved 1196, reused 0, downloaded 410, added 403
[Install deps and run eslint] Progress: resolved 1196, reused 0, downloaded 411, added 403
[Install deps and run eslint] Progress: resolved 1196, reused 0, downloaded 422, added 407
[Install deps and run eslint] Progress: resolved 1196, reused 0, downloaded 428, added 414
[Install deps and run eslint] Progress: resolved 1196, reused 0, downloaded 552, added 546
[Install deps and run eslint] Progress: resolved 1196, reused 0, downloaded 561, added 546
[Install deps and run eslint] Progress: resolved 1196, reused 0, downloaded 584, added 569
[Install deps and run eslint] Progress: resolved 1196, reused 0, downloaded 638, added 623
[Install deps and run eslint] Progress: resolved 1196, reused 0, downloaded 674, added 663
[Install deps and run eslint] Progress: resolved 1196, reused 0, downloaded 722, added 707
[Install deps and run eslint] Progress: resolved 1196, reused 0, downloaded 781, added 779
[Install deps and run eslint] Progress: resolved 1196, reused 0, downloaded 811, added 799
[Install deps and run eslint] Progress: resolved 1196, reused 0, downloaded 818, added 803
[Install deps and run eslint] Progress: resolved 1196, reused 0, downloaded 979, added 965
[Install deps and run eslint] Progress: resolved 1196, reused 0, downloaded 1036, added 1023
[Install deps and run eslint] Progress: resolved 1196, reused 0, downloaded 1081, added 1075
[Install deps and run eslint] Progress: resolved 1196, reused 0, downloaded 1156, added 1143
[Install deps and run eslint] Progress: resolved 1196, reused 0, downloaded 1182, added 1167
[Install deps and run eslint] Progress: resolved 1196, reused 0, downloaded 1196, added 1196, done
[Install deps and run eslint] .../node_modules/msw postinstall$ node -e "import('./config/scripts/postinstall.js').catch(() => void 0)"
[Install deps and run eslint] .../esbuild@0.25.12/node_modules/esbuild postinstall$ node install.js
.../sharp@0.34.5/node_modules/sharp install$ node install/check.js || npm run build
[Install deps and run eslint] .../esbuild@0.27.3/node_modules/esbuild postinstall$ node install.js
[Install deps and run eslint] .../esbuild@0.18.20/node_modules/esbuild postinstall$ node install.js
[Install deps and run eslint] .../esbuild@0.25.12/node_modules/esbuild postinstall: Done
.../node_modules/msw postinstall: Done
[Install deps and run eslint] .../sharp@0.34.5/node_modules/sharp install: Done
[Install deps and run eslint] .../node_modules/core-js-pure postinstall$ node -e "try{require('./postinstall')}catch(e){}"
[Install deps and run eslint] .../esbuild@0.18.20/node_modules/esbuild postinstall: Done
[Install deps and run eslint] .../esbuild@0.27.3/node_modules/esbuild postinstall: Done
[Install deps and run eslint] .../node_modules/core-js-pure postinstall: Done
[Install deps and run eslint]
devDependencies:
+ @workspace/eslint-config 0.0.0 <- packages/eslint-config
+ @workspace/typescript-config 0.0.0 <- packages/typescript-config
+ prettier 3.8.1
+ prettier-plugin-tailwindcss 0.7.4
+ turbo 2.9.6
+ typescript 5.9.3
+ vitest 4.1.5
[Install deps and run eslint] Done in 27s using pnpm v9.15.9
[Install deps and run eslint]
> open-git@0.0.1 lint /workspace
> turbo lint
[Install deps and run eslint]
Attention:
Turborepo now collects completely anonymous telemetry regarding usage.
This information is used to shape the Turborepo roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://turborepo.dev/docs/telemetry
[Install deps and run eslint]
• Packages in scope: @opengit/cli, @opengit/runner, @workspace/ci-runner-executor, @workspace/code-storage, @workspace/eslint-config, @workspace/git-graph, @workspace/git-indexing, @workspace/marketing, @workspace/typescript-config, @workspace/ui, @workspace/workflows, campfire-gateway, community, git-gateway, git-worker, managed-runner, playground, web
• Running lint in 18 packages
• Remote caching disabled
[Install deps and run eslint] @workspace/ui:lint: cache miss, executing 37cd0d50ae8b6a0e
[Install deps and run eslint] @workspace/git-graph:lint: cache miss, executing a84d93a82b401f01
@workspace/code-storage:lint: cache miss, executing 2d86046a5898a7cd
[Install deps and run eslint] @workspace/git-graph:lint:
@workspace/git-graph:lint: > @workspace/git-graph@0.0.0 lint /workspace/packages/git-graph
@workspace/git-graph:lint: > eslint
@workspace/git-graph:lint:
[Install deps and run eslint] @workspace/code-storage:lint:
@workspace/code-storage:lint: > @workspace/code-storage@0.0.0 lint /workspace/packages/code-storage
@workspace/code-storage:lint: > eslint
@workspace/code-storage:lint:
[Install deps and run eslint] @workspace/ui:lint:
@workspace/ui:lint: > @workspace/ui@0.0.0 lint /workspace/packages/ui
@workspace/ui:lint: > eslint
@workspace/ui:lint:
[Install deps and run eslint] @workspace/ui:lint:
@workspace/ui:lint: /workspace/packages/ui/src/components/appearance-menu-section.tsx
@workspace/ui:lint: 42:19 warning Error: Calling setState synchronously within an effect can trigger cascading renders
@workspace/ui:lint:
@workspace/ui:lint: Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
@workspace/ui:lint: * Update external systems with the latest state from React.
@workspace/ui:lint: * Subscribe for updates from some external system, calling setState in a callback function when external state changes.
@workspace/ui:lint:
@workspace/ui:lint: Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
@workspace/ui:lint:
@workspace/ui:lint: /workspace/packages/ui/src/components/appearance-menu-section.tsx:42:19
@workspace/ui:lint: 40 | // next-themes resolves the active value only on the client; defer reading it
@workspace/ui:lint: 41 | // until mounted to avoid a hydration mismatch on the highlighted cell.
@workspace/ui:lint: > 42 | useEffect(() => setMounted(true), [])
@workspace/ui:lint: | ^^^^^^^^^^ Avoid calling setState() directly within an effect
@workspace/ui:lint: 43 |
@workspace/ui:lint: 44 | const active = mounted ? theme : undefined
@workspace/ui:lint: 45 | const activeIndex = THEME_OPTIONS.findIndex((option) => option.value === active) react-hooks/set-state-in-effect
@workspace/ui:lint:
@workspace/ui:lint: /workspace/packages/ui/src/components/command-menu-context.tsx
@workspace/ui:lint: 68:7 warning Error: Calling setState synchronously within an effect can trigger cascading renders
@workspace/ui:lint:
@workspace/ui:lint: Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
@workspace/ui:lint: * Update external systems with the latest state from React.
@workspace/ui:lint: * Subscribe for updates from some external system, calling setState in a callback function when external state changes.
@workspace/ui:lint:
@workspace/ui:lint: Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
@workspace/ui:lint:
@workspace/ui:lint: /workspace/packages/ui/src/components/command-menu-context.tsx:68:7
@workspace/ui:lint: 66 | const anchor = anchorRef.current
@workspace/ui:lint: 67 | if (!anchor) {
@workspace/ui:lint: > 68 | setOffset(null)
@workspace/ui:lint: | ^^^^^^^^^ Avoid calling setState() directly within an effect
@workspace/ui:lint: 69 | return
@workspace/ui:lint: 70 | }
@workspace/ui:lint: 71 | const measure = () => { react-hooks/set-state-in-effect
@workspace/ui:lint:
@workspace/ui:lint: /workspace/packages/ui/src/hooks/dotmatrix-hooks.ts
@workspace/ui:lint: 39:7 warning Error: Calling setState synchronously within an effect can trigger cascading renders
@workspace/ui:lint:
@workspace/ui:lint: Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
@workspace/ui:lint: * Update external systems with the latest state from React.
@workspace/ui:lint: * Subscribe for updates from some external system, calling setState in a callback function when external state changes.
@workspace/ui:lint:
@workspace/ui:lint: Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
@workspace/ui:lint:
@workspace/ui:lint: /workspace/packages/ui/src/hooks/dotmatrix-hooks.ts:39:7
@workspace/ui:lint: 37 | useEffect(() => {
@workspace/ui:lint: 38 | if (!active) {
@workspace/ui:lint: > 39 | setPhase(0);
@workspace/ui:lint: | ^^^^^^^^ Avoid calling setState() directly within an effect
@workspace/ui:lint: 40 | return;
@workspace/ui:lint: 41 | }
@workspace/ui:lint: 42 | react-hooks/set-state-in-effect
@workspace/ui:lint: 127:7 warning Error: Calling setState synchronously within an effect can trigger cascading renders
@workspace/ui:lint:
@workspace/ui:lint: Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
@workspace/ui:lint: * Update external systems with the latest state from React.
@workspace/ui:lint: * Subscribe for updates from some external system, calling setState in a callback function when external state changes.
@workspace/ui:lint:
@workspace/ui:lint: Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
@workspace/ui:lint:
@workspace/ui:lint: /workspace/packages/ui/src/hooks/dotmatrix-hooks.ts:127:7
@workspace/ui:lint: 125 | activeRef.current = false;
@workspace/ui:lint: 126 | currentStepRef.current = idleStep;
@workspace/ui:lint: > 127 | setStep(idleStep);
@workspace/ui:lint: | ^^^^^^^ Avoid calling setState() directly within an effect
@workspace/ui:lint: 128 | return;
@workspace/ui:lint: 129 | }
@workspace/ui:lint: 130 | react-hooks/set-state-in-effect
@workspace/ui:lint:
@workspace/ui:lint: ✖ 4 problems (0 errors, 4 warnings)
@workspace/ui:lint:
[Install deps and run eslint] playground:lint: cache miss, executing 96629242835a5c22
[Install deps and run eslint] @workspace/marketing:lint: cache miss, executing 9d1ef7db0242f4cd
[Install deps and run eslint] playground:lint:
playground:lint: > playground@0.0.1 lint /workspace/apps/playground
playground:lint: > eslint
playground:lint:
[Install deps and run eslint] @workspace/marketing:lint:
@workspace/marketing:lint: > @workspace/marketing@0.0.0 lint /workspace/packages/marketing
@workspace/marketing:lint: > eslint
@workspace/marketing:lint:
[Install deps and run eslint] playground:lint:
playground:lint: /workspace/apps/playground/components/theme-toggle.tsx
playground:lint: 11:19 warning Error: Calling setState synchronously within an effect can trigger cascading renders
playground:lint:
playground:lint: Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
playground:lint: * Update external systems with the latest state from React.
playground:lint: * Subscribe for updates from some external system, calling setState in a callback function when external state changes.
playground:lint:
playground:lint: Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
playground:lint:
playground:lint: /workspace/apps/playground/components/theme-toggle.tsx:11:19
playground:lint: 9 | const { resolvedTheme, setTheme } = useTheme()
playground:lint: 10 | const [mounted, setMounted] = useState(false)
playground:lint: > 11 | useEffect(() => setMounted(true), [])
playground:lint: | ^^^^^^^^^^ Avoid calling setState() directly within an effect
playground:lint: 12 |
playground:lint: 13 | const isDark = mounted ? resolvedTheme === "dark" : true
playground:lint: 14 | react-hooks/set-state-in-effect
playground:lint:
playground:lint: ✖ 1 problem (0 errors, 1 warning)
playground:lint:
[Install deps and run eslint] @workspace/marketing:lint:
@workspace/marketing:lint: /workspace/packages/marketing/src/logo-shaders/ascii-shader.tsx
@workspace/marketing:lint: 23:7 warning 'DEFAULT_CONFIG' is assigned a value but never used @typescript-eslint/no-unused-vars
@workspace/marketing:lint: 92:3 warning Error: Cannot access refs during render
@workspace/marketing:lint:
@workspace/marketing:lint: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).
@workspace/marketing:lint:
@workspace/marketing:lint: /workspace/packages/marketing/src/logo-shaders/ascii-shader.tsx:92:3
@workspace/marketing:lint: 90 | const logoAnchorXRef = useRef(logoAnchorX)
@workspace/marketing:lint: 91 |
@workspace/marketing:lint: > 92 | configRef.current = config
@workspace/marketing:lint: | ^^^^^^^^^^^^^^^^^ Cannot update ref during render
@workspace/marketing:lint: 93 | themeRef.current = theme
@workspace/marketing:lint: 94 | logoAnchorXRef.current = logoAnchorX
@workspace/marketing:lint: 95 | react-hooks/refs
@workspace/marketing:lint: 93:3 warning Error: Cannot access refs during render
@workspace/marketing:lint:
@workspace/marketing:lint: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).
@workspace/marketing:lint:
@workspace/marketing:lint: /workspace/packages/marketing/src/logo-shaders/ascii-shader.tsx:93:3
@workspace/marketing:lint: 91 |
@workspace/marketing:lint: 92 | configRef.current = config
@workspace/marketing:lint: > 93 | themeRef.current = theme
@workspace/marketing:lint: | ^^^^^^^^^^^^^^^^ Cannot update ref during render
@workspace/marketing:lint: 94 | logoAnchorXRef.current = logoAnchorX
@workspace/marketing:lint: 95 |
@workspace/marketing:lint: 96 | const packKey = (col: number, row: number) => col * 100000 + row react-hooks/refs
@workspace/marketing:lint: 94:3 warning Error: Cannot access refs during render
@workspace/marketing:lint:
@workspace/marketing:lint: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).
@workspace/marketing:lint:
@workspace/marketing:lint: /workspace/packages/marketing/src/logo-shaders/ascii-shader.tsx:94:3
@workspace/marketing:lint: 92 | configRef.current = config
@workspace/marketing:lint: 93 | themeRef.current = theme
@workspace/marketing:lint: > 94 | logoAnchorXRef.current = logoAnchorX
@workspace/marketing:lint: | ^^^^^^^^^^^^^^^^^^^^^^ Cannot update ref during render
@workspace/marketing:lint: 95 |
@workspace/marketing:lint: 96 | const packKey = (col: number, row: number) => col * 100000 + row
@workspace/marketing:lint: 97 | react-hooks/refs
@workspace/marketing:lint:
@workspace/marketing:lint: /workspace/packages/marketing/src/logo-shaders/lines-shader.tsx
@workspace/marketing:lint: 70:3 warning Error: Cannot access refs during render
@workspace/marketing:lint:
@workspace/marketing:lint: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).
@workspace/marketing:lint:
@workspace/marketing:lint: /workspace/packages/marketing/src/logo-shaders/lines-shader.tsx:70:3
@workspace/marketing:lint: 68 | const clipToLogoBoundsRef = useRef(clipToLogoBounds)
@workspace/marketing:lint: 69 |
@workspace/marketing:lint: > 70 | configRef.current = config
@workspace/marketing:lint: | ^^^^^^^^^^^^^^^^^ Cannot update ref during render
@workspace/marketing:lint: 71 | svgScaleRef.current = svgScale
@workspace/marketing:lint: 72 | logoAnchorXRef.current = logoAnchorX
@workspace/marketing:lint: 73 | clipToLogoBoundsRef.current = clipToLogoBounds react-hooks/refs
@workspace/marketing:lint: 71:3 warning Error: Cannot access refs during render
@workspace/marketing:lint:
@workspace/marketing:lint: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).
@workspace/marketing:lint:
@workspace/marketing:lint: /workspace/packages/marketing/src/logo-shaders/lines-shader.tsx:71:3
@workspace/marketing:lint: 69 |
@workspace/marketing:lint: 70 | configRef.current = config
@workspace/marketing:lint: > 71 | svgScaleRef.current = svgScale
@workspace/marketing:lint: | ^^^^^^^^^^^^^^^^^^^ Cannot update ref during render
@workspace/marketing:lint: 72 | logoAnchorXRef.current = logoAnchorX
@workspace/marketing:lint: 73 | clipToLogoBoundsRef.current = clipToLogoBounds
@workspace/marketing:lint: 74 | themeRef.current = theme react-hooks/refs
@workspace/marketing:lint: 72:3 warning Error: Cannot access refs during render
@workspace/marketing:lint:
@workspace/marketing:lint: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).
@workspace/marketing:lint:
@workspace/marketing:lint: /workspace/packages/marketing/src/logo-shaders/lines-shader.tsx:72:3
@workspace/marketing:lint: 70 | configRef.current = config
@workspace/marketing:lint: 71 | svgScaleRef.current = svgScale
@workspace/marketing:lint: > 72 | logoAnchorXRef.current = logoAnchorX
@workspace/marketing:lint: | ^^^^^^^^^^^^^^^^^^^^^^ Cannot update ref during render
@workspace/marketing:lint: 73 | clipToLogoBoundsRef.current = clipToLogoBounds
@workspace/marketing:lint: 74 | themeRef.current = theme
@workspace/marketing:lint: 75 | svgPathRef.current = svgPath react-hooks/refs
@workspace/marketing:lint: 73:3 warning Error: Cannot access refs during render
@workspace/marketing:lint:
@workspace/marketing:lint: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).
@workspace/marketing:lint:
@workspace/marketing:lint: /workspace/packages/marketing/src/logo-shaders/lines-shader.tsx:73:3
@workspace/marketing:lint: 71 | svgScaleRef.current = svgScale
@workspace/marketing:lint: 72 | logoAnchorXRef.current = logoAnchorX
@workspace/marketing:lint: > 73 | clipToLogoBoundsRef.current = clipToLogoBounds
@workspace/marketing:lint: | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ Cannot update ref during render
@workspace/marketing:lint: 74 | themeRef.current = theme
@workspace/marketing:lint: 75 | svgPathRef.current = svgPath
@workspace/marketing:lint: 76 | svgWidthRef.current = svgWidth react-hooks/refs
@workspace/marketing:lint: 74:3 warning Error: Cannot access refs during render
@workspace/marketing:lint:
@workspace/marketing:lint: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).
@workspace/marketing:lint:
@workspace/marketing:lint: /workspace/packages/marketing/src/logo-shaders/lines-shader.tsx:74:3
@workspace/marketing:lint: 72 | logoAnchorXRef.current = logoAnchorX
@workspace/marketing:lint: 73 | clipToLogoBoundsRef.current = clipToLogoBounds
@workspace/marketing:lint: > 74 | themeRef.current = theme
@workspace/marketing:lint: | ^^^^^^^^^^^^^^^^ Cannot update ref during render
@workspace/marketing:lint: 75 | svgPathRef.current = svgPath
@workspace/marketing:lint: 76 | svgWidthRef.current = svgWidth
@workspace/marketing:lint: 77 | svgHeightRef.current = svgHeight react-hooks/refs
@workspace/marketing:lint: 75:3 warning Error: Cannot access refs during render
@workspace/marketing:lint:
@workspace/marketing:lint: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).
@workspace/marketing:lint:
@workspace/marketing:lint: /workspace/packages/marketing/src/logo-shaders/lines-shader.tsx:75:3
@workspace/marketing:lint: 73 | clipToLogoBoundsRef.current = clipToLogoBounds
@workspace/marketing:lint: 74 | themeRef.current = theme
@workspace/marketing:lint: > 75 | svgPathRef.current = svgPath
@workspace/marketing:lint: | ^^^^^^^^^^^^^^^^^^ Cannot update ref during render
@workspace/marketing:lint: 76 | svgWidthRef.current = svgWidth
@workspace/marketing:lint: 77 | svgHeightRef.current = svgHeight
@workspace/marketing:lint: 78 | react-hooks/refs
@workspace/marketing:lint: 76:3 warning Error: Cannot access refs during render
@workspace/marketing:lint:
@workspace/marketing:lint: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).
@workspace/marketing:lint:
@workspace/marketing:lint: /workspace/packages/marketing/src/logo-shaders/lines-shader.tsx:76:3
@workspace/marketing:lint: 74 | themeRef.current = theme
@workspace/marketing:lint: 75 | svgPathRef.current = svgPath
@workspace/marketing:lint: > 76 | svgWidthRef.current = svgWidth
@workspace/marketing:lint: | ^^^^^^^^^^^^^^^^^^^ Cannot update ref during render
@workspace/marketing:lint: 77 | svgHeightRef.current = svgHeight
@workspace/marketing:lint: 78 |
@workspace/marketing:lint: 79 | const mouseXRef = useRef(-1000) react-hooks/refs
@workspace/marketing:lint: 77:3 warning Error: Cannot access refs during render
@workspace/marketing:lint:
@workspace/marketing:lint: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).
@workspace/marketing:lint:
@workspace/marketing:lint: /workspace/packages/marketing/src/logo-shaders/lines-shader.tsx:77:3
@workspace/marketing:lint: 75 | svgPathRef.current = svgPath
@workspace/marketing:lint: 76 | svgWidthRef.current = svgWidth
@workspace/marketing:lint: > 77 | svgHeightRef.current = svgHeight
@workspace/marketing:lint: | ^^^^^^^^^^^^^^^^^^^^ Cannot update ref during render
@workspace/marketing:lint: 78 |
@workspace/marketing:lint: 79 | const mouseXRef = useRef(-1000)
@workspace/marketing:lint: 80 | const mouseYRef = useRef(-1000) react-hooks/refs
@workspace/marketing:lint:
@workspace/marketing:lint: ✖ 12 problems (0 errors, 12 warnings)
@workspace/marketing:lint:
[Install deps and run eslint] web:lint: cache miss, executing 93d9fe0957f33568
[Install deps and run eslint] community:lint: cache miss, executing 2dc4b204d62b7fed
[Install deps and run eslint] web:lint:
web:lint: > web@0.0.1 lint /workspace/apps/web
web:lint: > eslint
web:lint:
[Install deps and run eslint] community:lint:
community:lint: > community@0.0.1 lint /workspace/apps/community
community:lint: > eslint
community:lint:
[Install deps and run eslint] community:lint:
community:lint: /workspace/apps/community/components/post-header.tsx
community:lint: 10:11 warning Error: Cannot create components during render
community:lint:
community:lint: Components created during render will reset their state each time they are created. Declare components outside of render.
community:lint:
community:lint: /workspace/apps/community/components/post-header.tsx:10:11
community:lint: 8 | }
community:lint: 9 |
community:lint: > 10 | return <Skeleton />
community:lint: | ^^^^^^^^ This component is created during render
community:lint: 11 | }
community:lint: 12 |
community:lint:
community:lint: /workspace/apps/community/components/post-header.tsx:4:20
community:lint: 2 |
community:lint: 3 | export function PostHeader({ header }: { header?: string }) {
community:lint: > 4 | const Skeleton = getPostHeaderSkeleton(header)
community:lint: | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The component is created during render here
community:lint: 5 |
community:lint: 6 | if (!Skeleton) {
community:lint: 7 | return null react-hooks/static-components
community:lint:
community:lint: /workspace/apps/community/lib/posts.ts
community:lint: 82:24 warning '_content' is assigned a value but never used @typescript-eslint/no-unused-vars
community:lint: 82:39 warning '_toc' is assigned a value but never used @typescript-eslint/no-unused-vars
community:lint:
community:lint: ✖ 3 problems (0 errors, 3 warnings)
community:lint:
[Install deps and run eslint] web:lint:
web:lint: /workspace/apps/web/components/account-settings/account-settings-modal.tsx
web:lint: 64:17 warning Error: Calling setState synchronously within an effect can trigger cascading renders
web:lint:
web:lint: Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
web:lint: * Update external systems with the latest state from React.
web:lint: * Subscribe for updates from some external system, calling setState in a callback function when external state changes.
web:lint:
web:lint: Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
web:lint:
web:lint: /workspace/apps/web/components/account-settings/account-settings-modal.tsx:64:17
web:lint: 62 | const [renderKey, setRenderKey] = useState(active)
web:lint: 63 | useEffect(() => {
web:lint: > 64 | if (active) setRenderKey(active)
web:lint: | ^^^^^^^^^^^^ Avoid calling setState() directly within an effect
web:lint: 65 | }, [active])
web:lint: 66 |
web:lint: 67 | const close = () => { react-hooks/set-state-in-effect
web:lint:
web:lint: /workspace/apps/web/components/github-import-modal.tsx
web:lint: 38:15 warning Error: Calling setState synchronously within an effect can trigger cascading renders
web:lint:
web:lint: Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
web:lint: * Update external systems with the latest state from React.
web:lint: * Subscribe for updates from some external system, calling setState in a callback function when external state changes.
web:lint:
web:lint: Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
web:lint:
web:lint: /workspace/apps/web/components/github-import-modal.tsx:38:15
web:lint: 36 | const [mounted, setMounted] = useState(open)
web:lint: 37 | useEffect(() => {
web:lint: > 38 | if (open) setMounted(true)
web:lint: | ^^^^^^^^^^ Avoid calling setState() directly within an effect
web:lint: 39 | }, [open])
web:lint: 40 |
web:lint: 41 | const close = () => { react-hooks/set-state-in-effect
web:lint:
web:lint: ✖ 2 problems (0 errors, 2 warnings)
web:lint:
[Install deps and run eslint]
Tasks: 7 successful, 7 total
Cached: 0 cached, 7 total
Time: 40.987s