How duvancode/cloundserverextension works
Project type and purpose
• This is a Chrome Extension (manifest.json at the root) written in vanilla JavaScript.
• Purpose: a “Clound Server” UI that allows users to register/login (via traditional, OAuth2.0 or QR), upload/download files, and sync clipboard across devices by talking to an external backend service.
File structure
• Top‐level
• manifest.json – Chrome extension manifest
• package.json / build.js – build scripts or local dev tooling
• src/index.html, login.html, register.html – entry pages for the extension’s popup or UI panels
• src/css/… – style sheets (Tailwind + custom CSS)
• src/images/… – static assets
• src/libs/ – JavaScript modules organized by feature and layer
· home/, login/, register/ – each has components, events, lib wrappers
· services/general.service.js – HTTP/API calls to the external server
· utils/ – generic methods, string helpers, i18n (en.js, es.js), lang controller, config
README insights
• Describes features (registration, login, file upload, cloud clipboard).
• Notes a “front-end architecture proposal in vanilla JS.”
• No backend code here → the extension calls a remote API.
Elements
• UI → Events → Services → External API → Services → UI
• Background ↔ External API (for real-time clipboard sync)
• UI/Background ↔ chrome.storage or chrome.runtime
• Blue for UI/UI modules
• Green for services layer
• Yellow for utils/i18n
• Orange for Chrome APIs
• Red for external backend