You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2.**Create .env**: `cp .env.example .env` (configure `PUBLIC_APPWRITE_ENDPOINT` and `PUBLIC_CONSOLE_MODE`)
13
13
3.**Configure network access** (if using GitHub Actions or restricted environments):
14
-
- Ensure firewall/proxy allows access to: `pkg.pr.new`, `pkg.vc`, `registry.npmjs.org`
15
-
- These domains are required for dependencies: `@appwrite.io/console`, `@appwrite.io/pink-icons-svelte`, `@appwrite.io/pink-svelte`
16
-
- In GitHub Actions: Use `pnpm/action-setup@v4` which handles registry configuration
17
-
- If network errors persist, check proxy settings: `npm config get proxy` and `npm config get https-proxy`
14
+
- Ensure firewall/proxy allows access to: `pkg.pr.new`, `pkg.vc`, `registry.npmjs.org`
15
+
- These domains are required for dependencies: `@appwrite.io/console`, `@appwrite.io/pink-icons-svelte`, `@appwrite.io/pink-svelte`
16
+
- In GitHub Actions: Use `pnpm/action-setup@v4` which handles registry configuration
17
+
- If network errors persist, check proxy settings: `npm config get proxy` and `npm config get https-proxy`
18
18
4.**Install dependencies**: `pnpm install --frozen-lockfile` (if pkg.pr.new/pkg.vc fail due to network restrictions, installation may still succeed with cached versions)
19
19
20
20
### Development Commands
@@ -70,12 +70,12 @@ src/
70
70
## Common Pitfalls
71
71
72
72
1.**Blank page in dev**: Disable ad blockers if seeing "Failed to fetch dynamically imported module" (known SvelteKit issue)
73
-
2.**Network errors on install**:
74
-
- pkg.pr.new/pkg.vc deps may fail due to firewall/proxy restrictions
75
-
- Check access: `curl -I https://pkg.pr.new` and `curl -I https://pkg.vc`
76
-
- Configure proxy if needed: `npm config set proxy http://proxy:port` and `npm config set https-proxy http://proxy:port`
77
-
- GitHub Actions: Ensure runner has internet access; use `pnpm/action-setup@v4` action
78
-
- Local dev: Often safe to continue with cached versions if network fails
73
+
2.**Network errors on install**:
74
+
- pkg.pr.new/pkg.vc deps may fail due to firewall/proxy restrictions
75
+
- Check access: `curl -I https://pkg.pr.new` and `curl -I https://pkg.vc`
76
+
- Configure proxy if needed: `npm config set proxy http://proxy:port` and `npm config set https-proxy http://proxy:port`
77
+
- GitHub Actions: Ensure runner has internet access; use `pnpm/action-setup@v4` action
78
+
- Local dev: Often safe to continue with cached versions if network fails
79
79
3.**OOM on build**: Set `NODE_OPTIONS=--max_old_space_size=8192` (like Dockerfile does)
80
80
4.**Test failures**: Always use `pnpm run test` (sets TZ=EST), not `vitest` directly
81
81
5.**TS errors not showing**: Run `pnpm run check` explicitly (dev server doesn't always surface them)
0 commit comments