Update: prepared a source fix in the local checkout by replacing the deprecated request option with in . Added a regression test covering the request payload. Validation: focused test passed (1/1), full suite passed (45 files, 713 tests), and
> [email protected] lint
> eslint
/Users/vam/Documents/work/temp/f-prompts-chat/mdx-components.tsx
9:20 warning '_ref' is defined but never used @typescript-eslint/no-unused-vars
14:20 warning '_ref' is defined but never used @typescript-eslint/no-unused-vars
17:20 warning '_ref' is defined but never used @typescript-eslint/no-unused-vars
20:17 warning '_ref' is defined but never used @typescript-eslint/no-unused-vars
23:17 warning '_ref' is defined but never used @typescript-eslint/no-unused-vars
26:17 warning '_ref' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/packages/prompts.chat/scripts/generate-docs.ts
86:123 warning 'checker' is defined but never used @typescript-eslint/no-unused-vars
134:83 warning 'checker' is defined but never used @typescript-eslint/no-unused-vars
183:83 warning 'checker' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/packages/prompts.chat/src/cli/components/PromptDetail.tsx
66:10 warning 'compiledContent' is assigned a value but never used @typescript-eslint/no-unused-vars
234:35 warning 'platform' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/packages/prompts.chat/src/cli/components/PromptList.tsx
59:6 warning React Hook useEffect has a missing dependency: 'initializePrompts'. Either include it or remove the dependency array react-hooks/exhaustive-deps
65:6 warning React Hook useEffect has a missing dependency: 'applyFilters'. Either include it or remove the dependency array react-hooks/exhaustive-deps
/Users/vam/Documents/work/temp/f-prompts-chat/packages/prompts.chat/src/cli/components/RunPrompt.tsx
18:70 warning 'mediaUrl' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/packages/prompts.chat/src/cli/new.ts
89:12 warning 'error' is defined but never used @typescript-eslint/no-unused-vars
102:12 warning 'error' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/packages/prompts.chat/src/parser/index.ts
58:9 warning '_currentValue' is assigned a value but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/__tests__/api/leaderboard.test.ts
21:24 warning The `Function` type accepts any function-like value.
Prefer explicitly defining any function parameters and return type @typescript-eslint/no-unsafe-function-type
/Users/vam/Documents/work/temp/f-prompts-chat/src/__tests__/api/search.test.ts
172:11 warning 'data' is assigned a value but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/__tests__/api/user-notifications.test.ts
200:11 warning 'response' is assigned a value but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/__tests__/api/versions.test.ts
305:58 warning 'ops' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/app/[username]/opengraph-image.tsx
162:13 warning img elements must have an alt prop, either with meaningful text, or an empty string for decorative images jsx-a11y/alt-text
/Users/vam/Documents/work/temp/f-prompts-chat/src/app/about/page.tsx
6:10 warning 'ExternalLink' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/app/admin/page.tsx
191:9 warning Do not pass children as props. Instead, nest children between the opening and closing tags react/no-children-prop
/Users/vam/Documents/work/temp/f-prompts-chat/src/app/api/admin/embeddings/route.ts
40:18 warning 'error' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/app/api/admin/import-prompts/route.ts
103:28 warning 'request' is defined but never used @typescript-eslint/no-unused-vars
266:30 warning 'request' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/app/api/prompts/[id]/route.ts
103:24 warning '_embedding' is assigned a value but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/app/api/prompts/route.ts
455:50 warning '_e' is defined but never used @typescript-eslint/no-unused-vars
455:65 warning '_p' is defined but never used @typescript-eslint/no-unused-vars
455:81 warning '_u' is defined but never used @typescript-eslint/no-unused-vars
455:97 warning '_ua' is defined but never used @typescript-eslint/no-unused-vars
455:113 warning '_d' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/app/book/[slug]/page.tsx
156:15 warning Component definition is missing display name react/display-name
/Users/vam/Documents/work/temp/f-prompts-chat/src/app/book/page.tsx
249:15 warning Do not use an `<a>` element to navigate to `/kids/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages @next/next/no-html-link-for-pages
/Users/vam/Documents/work/temp/f-prompts-chat/src/app/brand/page.tsx
133:29 warning 'name' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/app/developers/page.tsx
32:5 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/app/developers/page.tsx:32:5
30 |
31 | useEffect(() => {
> 32 | setMounted(true);
| ^^^^^^^^^^ Avoid calling setState() directly within an effect
33 |
34 | // Check mobile
35 | const checkMobile = () => { react-hooks/set-state-in-effect
/Users/vam/Documents/work/temp/f-prompts-chat/src/app/embed/page.tsx
120:5 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/app/embed/page.tsx:120:5
118 | dark = window.matchMedia("(prefers-color-scheme: dark)").matches;
119 | }
> 120 | setIsDark(dark);
| ^^^^^^^^^ Avoid calling setState() directly within an effect
121 |
122 | // Set dark class on html element for portals (dropdowns, modals)
123 | if (dark) { react-hooks/set-state-in-effect
236:20 warning Compilation Skipped: Existing memoization could not be preserved
React Compiler has skipped optimizing this component because the existing manual memoization could not be preserved. This value was memoized in source but not in compilation output.
/Users/vam/Documents/work/temp/f-prompts-chat/src/app/embed/page.tsx:236:20
234 | const allContextPills = [...config.context, ...Array.from(selectedFiles)];
235 |
> 236 | const fileTree = useMemo(() => buildFileTree(config.filetree), [config.filetree]);
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Could not preserve existing memoization
237 |
238 | const renderTreeNode = (node: TreeNode, depth: number = 0): React.ReactNode => {
239 | const isSelected = selectedFiles.has(node.path); react-hooks/preserve-manual-memoization
236:67 warning Compilation Skipped: Existing memoization could not be preserved
React Compiler has skipped optimizing this component because the existing manual memoization could not be preserved. This dependency may be mutated later, which could cause the value to change unexpectedly.
/Users/vam/Documents/work/temp/f-prompts-chat/src/app/embed/page.tsx:236:67
234 | const allContextPills = [...config.context, ...Array.from(selectedFiles)];
235 |
> 236 | const fileTree = useMemo(() => buildFileTree(config.filetree), [config.filetree]);
| ^^^^^^ This dependency may be modified later
237 |
238 | const renderTreeNode = (node: TreeNode, depth: number = 0): React.ReactNode => {
239 | const isSelected = selectedFiles.has(node.path); react-hooks/preserve-manual-memoization
344:19 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
593:15 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
/Users/vam/Documents/work/temp/f-prompts-chat/src/app/kids/map/page.tsx
11:9 warning 't' is assigned a value but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/app/layout.tsx
11:10 warning 'AppBanner' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/app/page.tsx
32:9 warning 'aiGenerationEnabled' is assigned a value but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/app/presentation/page.tsx
52:63 warning `'` can be escaped with `'`, `‘`, `'`, `’` react/no-unescaped-entities
87:40 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
87:53 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
101:37 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
101:41 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
103:65 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
103:69 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
112:135 warning `'` can be escaped with `'`, `‘`, `'`, `’` react/no-unescaped-entities
169:29 warning `'` can be escaped with `'`, `‘`, `'`, `’` react/no-unescaped-entities
179:27 warning `'` can be escaped with `'`, `‘`, `'`, `’` react/no-unescaped-entities
179:122 warning `'` can be escaped with `'`, `‘`, `'`, `’` react/no-unescaped-entities
201:146 warning `'` can be escaped with `'`, `‘`, `'`, `’` react/no-unescaped-entities
/Users/vam/Documents/work/temp/f-prompts-chat/src/app/prompts/[id]/edit/page.tsx
33:9 warning 't' is assigned a value but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/app/prompts/[id]/opengraph-image.tsx
305:19 warning img elements must have an alt prop, either with meaningful text, or an empty string for decorative images jsx-a11y/alt-text
344:13 warning img elements must have an alt prop, either with meaningful text, or an empty string for decorative images jsx-a11y/alt-text
/Users/vam/Documents/work/temp/f-prompts-chat/src/app/prompts/[id]/page.tsx
8:10 warning 'ShareDropdown' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/admin/admin-tabs.tsx
42:5 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/admin/admin-tabs.tsx:42:5
40 |
41 | useEffect(() => {
> 42 | setMounted(true);
| ^^^^^^^^^^ Avoid calling setState() directly within an effect
43 | updateTabFromHash();
44 | window.addEventListener("hashchange", updateTabFromHash);
45 | return () => { react-hooks/set-state-in-effect
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/admin/users-table.tsx
75:9 warning 'tCommon' is assigned a value but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/book/elements/ai-demos.tsx
3:20 warning 'useMemo' is defined but never used @typescript-eslint/no-unused-vars
8:51 warning 'Capability' is defined but never used @typescript-eslint/no-unused-vars
71:80 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
71:96 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
89:100 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
89:116 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/book/elements/chain-demos.tsx
5:65 warning 'ArrowRight' is defined but never used @typescript-eslint/no-unused-vars
5:77 warning 'ArrowDown' is defined but never used @typescript-eslint/no-unused-vars
6:10 warning 'useTranslations' is defined but never used @typescript-eslint/no-unused-vars
227:113 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
227:131 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/book/elements/chain-error-demo.tsx
5:65 warning 'ArrowRight' is defined but never used @typescript-eslint/no-unused-vars
7:31 warning 'ChainScenario' is defined but never used @typescript-eslint/no-unused-vars
7:51 warning 'ChainStep' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/book/elements/chain.tsx
7:31 warning 'ChainType' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/book/elements/challenge.tsx
65:6 warning React Hook useEffect has a missing dependency: 'handleSubmit'. Either include it or remove the dependency array react-hooks/exhaustive-deps
121:6 warning React Hook useCallback has a missing dependency: 't'. Either include it or remove the dependency array react-hooks/exhaustive-deps
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/book/elements/context-demos.tsx
3:20 warning 'useMemo' is defined but never used @typescript-eslint/no-unused-vars
7:76 warning 'SummarizationStrategy' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/book/elements/demos.tsx
43:7 warning 'sampleTokenizations' is assigned a value but never used @typescript-eslint/no-unused-vars
67:7 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/book/elements/demos.tsx:67:7
65 | const sample = currentData.samples[currentData.default];
66 | if (sample) {
> 67 | setInput(sample.text);
| ^^^^^^^^ Avoid calling setState() directly within an effect
68 | setTokens(sample.tokens);
69 | }
70 | }, [locale, currentData]); react-hooks/set-state-in-effect
292:71 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
292:96 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
537:66 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
537:77 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
548:49 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
548:66 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
768:7 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/book/elements/demos.tsx:768:7
766 | timer = setTimeout(() => setStep(s => s + 1), 2500);
767 | } else if (step >= iterations.length - 1) {
> 768 | setIsPlaying(false);
| ^^^^^^^^^^^^ Avoid calling setState() directly within an effect
769 | }
770 | return () => clearTimeout(timer);
771 | }, [isPlaying, step, iterations.length]); react-hooks/set-state-in-effect
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/book/elements/diff-view.tsx
3:10 warning 'cn' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/book/elements/lists.tsx
4:10 warning 'useTranslations' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/book/elements/media-demos.tsx
3:31 warning 'useMemo' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/book/elements/navigation.tsx
6:31 warning 'BookPart' is defined but never used @typescript-eslint/no-unused-vars
46:21 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
47:21 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/book/elements/principles.tsx
6:31 warning 'Principle' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/book/sidebar.tsx
49:16 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/book/sidebar.tsx:49:16
47 | useEffect(() => {
48 | const saved = localStorage.getItem(BOOKMARK_KEY);
> 49 | if (saved) setBookmark(saved);
| ^^^^^^^^^^^ Avoid calling setState() directly within an effect
50 | }, []);
51 |
52 | const saveBookmark = useCallback((slug: string) => { react-hooks/set-state-in-effect
107:33 warning Compilation Skipped: Existing memoization could not be preserved
React Compiler has skipped optimizing this component because the existing manual memoization could not be preserved. The inferred dependencies did not match the manually specified dependencies, which could cause the value to change more or less frequently than expected. The inferred dependency was `getChapterTitle`, but the source dependencies were [searchQuery]. Inferred different dependency than source.
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/book/sidebar.tsx:107:33
105 |
106 | // Filter parts and chapters based on search query
> 107 | const filteredParts = useMemo(() => {
| ^^^^^^^
> 108 | if (!searchQuery.trim()) return parts;
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 109 |
…
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 124 | .filter((part) => part.chapters.length > 0);
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 125 | }, [searchQuery]);
| ^^^^ Could not preserve existing manual memoization
126 |
127 | return (
128 | <nav className="space-y-4 pr-4"> react-hooks/preserve-manual-memoization
125:6 warning React Hook useMemo has a missing dependency: 'getChapterTitle'. Either include it or remove the dependency array react-hooks/exhaustive-deps
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/comments/comment-item.tsx
106:12 warning '_replies' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/comments/comment-section.tsx
51:6 warning React Hook useEffect has a missing dependency: 'fetchComments'. Either include it or remove the dependency array react-hooks/exhaustive-deps
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/developers/embed-designer.tsx
20:10 warning 'Copy' is defined but never used @typescript-eslint/no-unused-vars
112:9 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/developers/embed-designer.tsx:112:9
110 | try {
111 | const parsed = JSON.parse(saved);
> 112 | setConfig({ ...defaultConfig, ...parsed });
| ^^^^^^^^^ Avoid calling setState() directly within an effect
113 | if (!MODELS.find(m => m.value === parsed.model)) {
114 | setCustomModel(parsed.model);
115 | } react-hooks/set-state-in-effect
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/developers/prompt-tokenizer.tsx
215:5 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/developers/prompt-tokenizer.tsx:215:5
213 | // Load history and settings on mount
214 | useEffect(() => {
> 215 | setHistory(loadHistory());
| ^^^^^^^^^^ Avoid calling setState() directly within an effect
216 | const settings = loadSettings();
217 | setContextWindow(settings.contextWindow);
218 | setInputPrice(settings.inputPrice); react-hooks/set-state-in-effect
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/ide/examples/audio.ts
64:1 warning Assign object to a variable before exporting as module default import/no-anonymous-default-export
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/ide/examples/chat.ts
24:1 warning Assign object to a variable before exporting as module default import/no-anonymous-default-export
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/ide/examples/default.ts
18:7 warning 'translatePrompt' is assigned a value but never used @typescript-eslint/no-unused-vars
20:1 warning Assign object to a variable before exporting as module default import/no-anonymous-default-export
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/ide/examples/image.ts
80:1 warning Assign object to a variable before exporting as module default import/no-anonymous-default-export
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/ide/examples/video.ts
72:1 warning Assign object to a variable before exporting as module default import/no-anonymous-default-export
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/ide/prompt-ide.tsx
68:10 warning 'isRunning' is assigned a value but never used @typescript-eslint/no-unused-vars
317:6 warning React Hook useCallback has missing dependencies: 'formatOutput' and 'session?.user'. Either include them or remove the dependency array react-hooks/exhaustive-deps
376:6 warning React Hook useEffect has a missing dependency: 'runCode'. Either include it or remove the dependency array react-hooks/exhaustive-deps
817:42 warning 'monaco' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/elements/drag-drop-prompt.tsx
53:9 warning 'itemRefs' is assigned a value but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/elements/example-matcher.tsx
58:7 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/elements/example-matcher.tsx:58:7
56 | useEffect(() => {
57 | if (!levelSlug) {
> 58 | setIsLoaded(true);
| ^^^^^^^^^^^ Avoid calling setState() directly within an effect
59 | return;
60 | }
61 | const saved = getComponentState<SavedState>(levelSlug, componentId); react-hooks/set-state-in-effect
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/elements/level-complete.tsx
34:7 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/elements/level-complete.tsx:34:7
32 | if (stars > existingStars) {
33 | completeLevel(levelSlug, stars);
> 34 | setShowConfetti(true);
| ^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
35 |
36 | // Track level completion
37 | const level = getLevelBySlug(levelSlug); react-hooks/set-state-in-effect
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/elements/level-slides.tsx
23:41 warning 'levelSlug' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/elements/progress-map.tsx
11:10 warning 'Button' is defined but never used @typescript-eslint/no-unused-vars
19:3 warning 'PixelRobot' is defined but never used @typescript-eslint/no-unused-vars
36:5 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/elements/progress-map.tsx:36:5
34 |
35 | useEffect(() => {
> 36 | setProgress(getProgress());
| ^^^^^^^^^^^ Avoid calling setState() directly within an effect
37 | analyticsKids.viewMap();
38 | }, []);
39 | react-hooks/set-state-in-effect
221:10 warning 'generatePathD' is defined but never used @typescript-eslint/no-unused-vars
486:5 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/elements/progress-map.tsx:486:5
484 |
485 | useEffect(() => {
> 486 | setUnlocked(isLevelUnlocked(level.slug));
| ^^^^^^^^^^^ Avoid calling setState() directly within an effect
487 | }, [level.slug, progress]);
488 |
489 | const state = !unlocked ? "locked" : isCompleted ? "completed" : "available"; react-hooks/set-state-in-effect
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/elements/prompt-doctor.tsx
54:7 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/elements/prompt-doctor.tsx:54:7
52 | useEffect(() => {
53 | if (!levelSlug) {
> 54 | setIsLoaded(true);
| ^^^^^^^^^^^ Avoid calling setState() directly within an effect
55 | return;
56 | }
57 | const saved = getComponentState<SavedState>(levelSlug, componentId); react-hooks/set-state-in-effect
101:9 warning 'currentPrompt' is assigned a value but never used @typescript-eslint/no-unused-vars
164:11 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
164:32 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/elements/prompt-lab.tsx
56:7 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/elements/prompt-lab.tsx:56:7
54 | useEffect(() => {
55 | if (!levelSlug) {
> 56 | setIsLoaded(true);
| ^^^^^^^^^^^ Avoid calling setState() directly within an effect
57 | return;
58 | }
59 | const saved = getComponentState<SavedState>(levelSlug, componentId); react-hooks/set-state-in-effect
143:11 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
143:32 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
163:50 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
163:73 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/elements/prompt-parts.tsx
57:7 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/elements/prompt-parts.tsx:57:7
55 | useEffect(() => {
56 | if (!levelSlug) {
> 57 | setIsLoaded(true);
| ^^^^^^^^^^^ Avoid calling setState() directly within an effect
58 | return;
59 | }
60 | const saved = getComponentState<SavedState>(levelSlug, componentId); react-hooks/set-state-in-effect
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/elements/prompt-vs-mistake.tsx
51:7 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/elements/prompt-vs-mistake.tsx:51:7
49 |
50 | if (!levelSlug) {
> 51 | setOrder(randomOrder);
| ^^^^^^^^ Avoid calling setState() directly within an effect
52 | setIsLoaded(true);
53 | return;
54 | } react-hooks/set-state-in-effect
190:23 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
190:30 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
291:10 warning 'PixelThinkingIcon' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/elements/step-by-step.tsx
54:7 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/elements/step-by-step.tsx:54:7
52 | useEffect(() => {
53 | if (!levelSlug) {
> 54 | setIsLoaded(true);
| ^^^^^^^^^^^ Avoid calling setState() directly within an effect
55 | return;
56 | }
57 | const saved = getComponentState<SavedState>(levelSlug, componentId); react-hooks/set-state-in-effect
138:60 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
138:73 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
150:47 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
150:60 warning `"` can be escaped with `"`, `“`, `"`, `”` react/no-unescaped-entities
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/elements/word-predictor.tsx
55:7 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/elements/word-predictor.tsx:55:7
53 | useEffect(() => {
54 | if (!levelSlug) {
> 55 | setIsLoaded(true);
| ^^^^^^^^^^^ Avoid calling setState() directly within an effect
56 | return;
57 | }
58 | const saved = getComponentState<SavedState>(levelSlug, componentId); react-hooks/set-state-in-effect
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/layout/background-music.tsx
64:7 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/layout/background-music.tsx:64:7
62 |
63 | if (savedVolume) {
> 64 | setVolume(parseFloat(savedVolume));
| ^^^^^^^^^ Avoid calling setState() directly within an effect
65 | }
66 |
67 | // Default to enabled if not set react-hooks/set-state-in-effect
88:6 warning React Hook useEffect has a missing dependency: 'volume'. Either include it or remove the dependency array react-hooks/exhaustive-deps
148:9 warning 'setIsPlaying' is assigned a value but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/layout/kids-header.tsx
27:5 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/layout/kids-header.tsx:27:5
25 |
26 | useEffect(() => {
> 27 | setStars(getTotalStars());
| ^^^^^^^^ Avoid calling setState() directly within an effect
28 | setCompleted(getCompletedLevelsCount());
29 | }, []);
30 | react-hooks/set-state-in-effect
48:9 warning Do not use an `<a>` element to navigate to `/kids/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages @next/next/no-html-link-for-pages
81:13 warning Do not use an `<a>` element to navigate to `/kids/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages @next/next/no-html-link-for-pages
94:13 warning Do not use an `<a>` element to navigate to `/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages @next/next/no-html-link-for-pages
94:13 warning Do not use an `<a>` element to navigate to `/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages @next/next/no-html-link-for-pages
126:19 warning Do not use an `<a>` element to navigate to `/kids/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages @next/next/no-html-link-for-pages
142:19 warning Do not use an `<a>` element to navigate to `/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages @next/next/no-html-link-for-pages
142:19 warning Do not use an `<a>` element to navigate to `/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages @next/next/no-html-link-for-pages
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/layout/level-content-wrapper.tsx
19:73 warning '_levelNumber' is defined but never used @typescript-eslint/no-unused-vars
25:24 warning '_completedSections' is assigned a value but never used @typescript-eslint/no-unused-vars
27:24 warning '_isSectionComplete' is assigned a value but never used @typescript-eslint/no-unused-vars
158:9 warning '_handleMarkComplete' is assigned a value but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/providers/level-context.tsx
49:7 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/providers/level-context.tsx:49:7
47 | useEffect(() => {
48 | if (initialSlug) {
> 49 | setLevelSlug(initialSlug);
| ^^^^^^^^^^^^ Avoid calling setState() directly within an effect
50 | }
51 | }, [initialSlug]);
52 | react-hooks/set-state-in-effect
55:5 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/kids/providers/level-context.tsx:55:5
53 | // Reset section progress when level changes
54 | useEffect(() => {
> 55 | setCurrentSection(0);
| ^^^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
56 | setCompletedSections(new Set());
57 | setSectionsWithRequirements(new Set());
58 | }, [levelSlug]); react-hooks/set-state-in-effect
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/layout/analytics.tsx
12:10 warning 'hasConsent' is assigned a value but never used @typescript-eslint/no-unused-vars
15:5 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/layout/analytics.tsx:15:5
13 |
14 | useEffect(() => {
> 15 | setHasConsent(getCookieConsent() === "accepted");
| ^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
16 | }, []);
17 |
18 | return ( react-hooks/set-state-in-effect
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/layout/announcement-banner.tsx
93:21 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/layout/announcement-banner.tsx:93:21
91 | if (!storageKey) return;
92 | const dismissed = localStorage.getItem(storageKey);
> 93 | if (!dismissed) setIsVisible(true);
| ^^^^^^^^^^^^ Avoid calling setState() directly within an effect
94 | }, [storageKey]);
95 |
96 | if (!announcement || !isVisible || branding.useCloneBranding || hideViaQuery) { react-hooks/set-state-in-effect
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/layout/app-banner.tsx
53:5 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/layout/app-banner.tsx:53:5
51 | const dismissed = localStorage.getItem(STORAGE_KEY);
52 | const isAppleUser = isAppleDevice();
> 53 | setIsApple(isAppleUser);
| ^^^^^^^^^^ Avoid calling setState() directly within an effect
54 |
55 | if (isAppleUser && !dismissed) {
56 | setIsVisible(true); react-hooks/set-state-in-effect
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/layout/cookie-consent.tsx
23:5 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/layout/cookie-consent.tsx:23:5
21 |
22 | useEffect(() => {
> 23 | setConsent(getCookieConsent());
| ^^^^^^^^^^ Avoid calling setState() directly within an effect
24 | }, []);
25 |
26 | const handleAccept = () => { react-hooks/set-state-in-effect
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/layout/extension-link.tsx
21:7 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/layout/extension-link.tsx:21:7
19 | useEffect(() => {
20 | if (isFirefoxBrowser()) {
> 21 | setBrowserType("firefox");
| ^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
22 | } else if (isChromeBrowser()) {
23 | setBrowserType("chrome");
24 | } react-hooks/set-state-in-effect
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/layout/header.tsx
112:9 warning 'isOAuth' is assigned a value but never used @typescript-eslint/no-unused-vars
127:7 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/layout/header.tsx:127:7
125 | useEffect(() => {
126 | if (isFirefoxBrowser()) {
> 127 | setBrowserType("firefox");
| ^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
128 | } else if (isChromeBrowser()) {
129 | setBrowserType("chrome");
130 | } react-hooks/set-state-in-effect
269:21 warning Do not use an `<a>` element to navigate to `/kids/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages @next/next/no-html-link-for-pages
465:21 warning Do not use an `<a>` element to navigate to `/kids/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages @next/next/no-html-link-for-pages
501:13 warning Do not use an `<a>` element to navigate to `/kids/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages @next/next/no-html-link-for-pages
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/mcp/mcp-server-popup.tsx
24:7 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
29:7 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/prompts/audio-player.tsx
50:7 warning Error: Calling setState synchronously within an effect can trigger cascading renders
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:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
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).
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/prompts/audio-player.tsx:50:7
48 | animationRef.current = null;
49 | }
> 50 | setAnimatedHeights(baseHeights.map(h => h * 0.5));
| ^^^^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
51 | return;
52 | }
53 | react-hooks/set-state-in-effect
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/prompts/examples-slider.tsx
71:15 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/prompts/infinite-prompt-list.tsx
56:9 warning '_searchParams' is assigned a value but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/prompts/media-generator.tsx
26:15 warning 'WebSocketHandler' is defined but never used @typescript-eslint/no-unused-vars
437:17 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/prompts/prompt-builder.tsx
5:41 warning 'ChevronRight' is defined but never used @typescript-eslint/no-unused-vars
123:6 warning React Hook useEffect has missing dependencies: 'isLoading' and 'sendMessageWithContent'. Either include them or remove the dependency array react-hooks/exhaustive-deps
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/prompts/prompt-card.tsx
92:9 warning '_locale' is assigned a value but never used @typescript-eslint/no-unused-vars
105:10 warning '_isVisible' is assigned a value but never used @typescript-eslint/no-unused-vars
208:15 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/prompts/prompt-connections.tsx
852:21 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/prompts/prompt-form.tsx
27:3 warning 'DEFAULT_SKILL_FILE' is defined but never used @typescript-eslint/no-unused-vars
182:23 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
261:21 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/prompts/run-prompt-button.tsx
303:6 warning React Hook useCallback has missing dependencies: 'description' and 'title'. Either include them or remove the dependency array react-hooks/exhaustive-deps
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/prompts/skill-editor.tsx
375:11 warning '_ext' is assigned a value but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/prompts/variable-hint.tsx
42:5 warning 'v' is defined but never used @typescript-eslint/no-unused-vars
85:5 warning 'v' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/prompts/widget-card.tsx
21:10 warning 'copied' is assigned a value but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/providers/theme-styles.tsx
13:29 warning '_props' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/ui/diff-view.tsx
93:59 warning 'mode' is assigned a value but never used @typescript-eslint/no-unused-vars
151:38 warning 'language' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/components/ui/json-tree-view.tsx
110:58 warning '_isLast' is assigned a value but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/i18n/request.ts
53:7 warning 'detectedFromBrowser' is assigned a value but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/lib/ai/embeddings.ts
290:47 warning '_count' is defined but never used @typescript-eslint/no-unused-vars
290:55 warning 'embedding' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/lib/ai/prompt-builder-tools.ts
414:16 warning 'error' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/lib/plugins/media-generators/fal.ts
211:19 warning '_event' is defined but never used @typescript-eslint/no-unused-vars
211:41 warning '_callbacks' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/lib/plugins/storage/url.ts
15:16 warning 'file' is defined but never used @typescript-eslint/no-unused-vars
/Users/vam/Documents/work/temp/f-prompts-chat/src/lib/webhook.ts
179:22 warning 'c' is assigned a value but never used @typescript-eslint/no-unused-vars
✖ 206 problems (0 errors, 206 warnings) exited 0 with existing warnings. The live deployment still needs a redeploy before the two buttons can be re-tested; no PR was pushed from this account.