docs: update IDEA.md to mention TypeScript and pnpm

This commit is contained in:
2026-02-26 01:36:07 +01:00
parent 2b1838b0eb
commit 8214079093
+2 -2
View File
@@ -1,3 +1,3 @@
Lightweigh app that i will run on android. Built using react (not react-native), capacitor for the wrapper and ill run android studio myself in the end for the actual apk generation. It is a chat app to chat with locally (or remotely) hosted llms. When the user enters, if there is no memory of the last connection, it asks for a api endpoint (openai-like). the user provides it and they have a smal top left button to open a drawer with all sessions (also buttons to add/remove sessions). The actual chat window will be very minimal. The theme will be dark/black. there should be a "save conversation" button that exports it as some form of file (.log?.txt?.md?). the communication with the llm api should be something simple, if it was a bash program, i'd literally just wrap user prompts in a curl template and extract the "content" from the output, for a react app you figure the get/post. oh, also an option to add custom system prompts / inject my own prompts. Lightweigh app that i will run on android. Built using react (not react-native) with TypeScript, capacitor for the wrapper and ill run android studio myself in the end for the actual apk generation. It is a chat app to chat with locally (or remotely) hosted llms. When the user enters, if there is no memory of the last connection, it asks for a api endpoint (openai-like). the user provides it and they have a smal top left button to open a drawer with all sessions (also buttons to add/remove sessions). The actual chat window will be very minimal. The theme will be dark/black. there should be a "save conversation" button that exports it as some form of file (.log?.txt?.md?). the communication with the llm api should be something simple, if it was a bash program, i'd literally just wrap user prompts in a curl template and extract the "content" from the output, for a react app you figure the get/post. oh, also an option to add custom system prompts / inject my own prompts.
codebase rules: it needs to be simple. it must be modular. when making functions, think if there isn't a similar one that you can abstract for both usecases. it needs unit tests. codebase rules: it needs to be simple. it must be modular. when making functions, think if there isn't a similar one that you can abstract for both usecases. it needs unit tests. uses pnpm for package management.