3 Commits

Include renames

Author	SHA1	Message	Date
James BruntonandGitHub	1816bad1ba	Unified auth for portal and editor (#6725) ... # Description of Changes Refactor frontend auth to the shared folder and hook it up to both the portal and editor so they share the same system. Also adds various tasks to help run the portal, including `task dev:portal` to spawn the portal with the backend, and `task dev:portal:proxy` to spawn the editor, portal and backend, and a reverse proxy (at localhost:3000) to allow you to use both at once to simulate how this will actually be deployed, allowing you to check whether the seamless transition between the two actually works.	2026-06-22 16:22:36 +00:00
3 people	0a50e765b7	Restructure/frontend editor (#6404) ... ## Move editor under `frontend/editor/` Pure restructure: `frontend/` becomes the workspace, `frontend/editor/` holds the PDF editor. 1775 file renames + 40 wiring edits. No logic changes. ### Why `frontend/` is currently the editor — its `src/`, `public/`, `src-tauri/`, config files all sit at the root. Promoting `frontend/` to a workspace and putting the editor in a sibling folder leaves room for future apps to drop in alongside it, sharing one `package.json` / `node_modules` / lint config / Storybook. ### What moves frontend/ ├── editor/ ← NEW: everything editor-specific │ ├── src/ ← was frontend/src/ │ ├── public/ ← was frontend/public/ │ ├── src-tauri/ ← was frontend/src-tauri/ │ ├── index.html, vite.config.ts, vitest.config.ts, playwright.config.ts │ ├── tsconfig*.json, tailwind.config.js, postcss.config.js │ ├── scripts/ │ ├── .env, .env.desktop, .env.saas │ └── DeveloperGuide.md ├── package.json, package-lock.json, node_modules/ ← workspace install ├── eslint.config.mjs, .prettierrc, .prettierignore ← shared tooling ├── .gitignore └── README.md ### Wiring edits (40 files) - `.taskfiles/frontend.yml`, `desktop.yml`, `e2e.yml` - `build.gradle`, `app/core/build.gradle` - `eslint.config.mjs`, `frontend/package.json`, `.gitignore`, `.prettierignore` - `docker/frontend/Dockerfile` - 8 `.github/workflows/*.yml`, plus `.github/dependabot.yml`, `.github/config/.files.yaml`, `.github/labeler-config-srvaroa.yml` - `scripts/translations/**` - Docs: `AGENTS.md`, `CLAUDE.md`, `ADDING_TOOLS.md`, `DeveloperGuide.md`, `WINDOWS_SIGNING.md`, `devGuide/HowToAddNewLanguage.md`, `frontend/README.md`, `frontend/editor/DeveloperGuide.md` Plus 3 renamed + edited: `editor/vite.config.ts` (env path + node_modules walk-up), `editor/scripts/setup-env.mts` (renamed from `.ts` for `import.meta.url`), `editor/scripts/build-provisioner.mjs` (resolve src-tauri relative to script). ### Verification | Check | Result | |---|---| | `task frontend:typecheck:all` (6 variants) | exit 0 | | `task frontend:lint` (eslint + dpdm) | exit 0 | | `task frontend:format:check` | exit 0 | | `task frontend:test` | 657 tests pass, 50 files | | `task frontend:build:{core,proprietary,saas,desktop,prototypes}` | all green | | `task desktop:build` | full Tauri pipeline → `Stirling-PDF_2.11.0_x64_en-US.msi` | | `playwright test --list --project=stubbed` | 172 tests discovered | `task desktop:build` exercises the heaviest path — Rust + WiX + MSI bundle against the moved `editor/src-tauri/`. If anything in the restructure was wrong it wouldn't have built. ### Test plan - [ ] `frontend-validation.yml` green - [ ] `e2e-stubbed.yml` green - [ ] `tauri-build.yml` green on at least one platform - [ ] `check_toml.yml` runs on a translation-touching PR --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-22 13:40:34 +01:00
James BruntonandGitHub	8674765528	Add system for managing env vars (#5902) ... # Description of Changes Previously, `VITE_*` environment variables were scattered across the codebase with hardcoded fallback values inline (e.g. `import.meta.env.VITE_STRIPE_KEY || 'pk_live_...'`). This made it unclear which variables were required, what they were for, and caused real keys to be silently used in builds where they hadn't been explicitly configured. ## What's changed I've added `frontend/.env.example` and `frontend/.env.desktop.example`, which declare every `VITE_*` variable the app uses, with comments explaining each one and sensible defaults where applicable. These are the source of truth for what's required. I've added a setup script which runs before `npm run dev`, `build`, `tauri-dev`, and all `tauri-build*` commands. It: - Creates your local `.env` / `.env.desktop` from the example files on first run, so you don't need to do anything manually - Errors if you're missing keys that the example defines (e.g. after pulling changes that added a new variable). These can either be manually-set env vars, or in your `.env` file (env vars take precedence over `.env` file vars when running) - Warns if you have `VITE_*` variables set in your environment that aren't listed in any example file I've removed all `|| 'hardcoded-value'` defaults from source files because they are not necessary in this system, as all variables must be explicitly set (they can be set to `VITE_ENV_VAR=`, just as long as the variable actually exists). I think this system will make it really obvious exactly what you need to set and what's actually running in the code. I've added a test that checks that every `import.meta.env.VITE_*` reference found in source is present in at least one example file, so new variables can't be added without being documented. ## For contributors New contributors shouldn't need to do anything - `npm run dev` will create your `.env` automatically. If you already have a `.env` file in the `frontend/` folder, you may well need to update it to make the system happy. Here's an example output from running `npm run dev` with an old `.env` file: ``` $ npm run dev > frontend@0.1.0 dev > npm run prep && vite > frontend@0.1.0 prep > tsx scripts/setup-env.ts && npm run generate-icons setup-env: see frontend/README.md#environment-variables for documentation setup-env: .env is missing keys from config/.env.example: VITE_GOOGLE_DRIVE_CLIENT_ID VITE_GOOGLE_DRIVE_API_KEY VITE_GOOGLE_DRIVE_APP_ID VITE_PUBLIC_POSTHOG_KEY VITE_PUBLIC_POSTHOG_HOST Add them manually or delete your local file to re-copy from the example. setup-env: the following VITE_ vars are set but not listed in any example file: VITE_DEV_BYPASS_AUTH Add them to config/.env.example or config/.env.desktop.example if they are required. ``` If you add a new `VITE_*` variable to the codebase, add it to the appropriate `frontend/config/.env.example` file or the test will fail.	2026-03-12 13:03:44 +00:00