widefleet-darwin-arm64 0.3.3 → 0.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -7,7 +7,8 @@ access to a Widefleet installation; if you do not have one yet, start with the
7
7
  ## Install the CLI
8
8
 
9
9
  The CLI supports Linux x64 with glibc, macOS on Apple Silicon and Intel,
10
- and Windows x64. Install Node.js 26 and pnpm 12.4.2 for app development.
10
+ and Windows x64. For app development, use Node.js 22.18 or newer and an existing
11
+ pnpm 10.34.5 or newer installation.
11
12
 
12
13
  ```sh
13
14
  pnpm add --global widefleet
@@ -18,7 +19,7 @@ If pnpm reports that its global bin directory is missing from PATH, run `pnpm se
18
19
 
19
20
  To update, rerun the install command. To uninstall, run `pnpm remove --global widefleet`. pnpm owns the complete installation directory; keep its package contents together.
20
21
 
21
- The CLI includes its native executable, bundler and SvelteKit starter. App
22
+ The CLI includes its native executable, bundler and app starters. App
22
23
  developers do not need Docker or a checkout of the platform repository when
23
24
  connecting to an existing installation.
24
25
 
@@ -31,6 +32,15 @@ pnpm install --frozen-lockfile
31
32
  pnpm dev
32
33
  ```
33
34
 
35
+ This creates the default SvelteKit project. For React, see the
36
+ [TanStack Start template and release requirements](https://widefleet.com/docs/reference/cli#create-a-project).
37
+
38
+ Both projects pin pnpm 12.4.2 in `packageManager`. With pnpm's default version
39
+ management, an existing pnpm 10.34.5 or newer installation automatically downloads
40
+ and runs that version when you run a command inside the project.
41
+ pnpm 10.34.5 includes the [version-switching fix](https://github.com/pnpm/pnpm/releases/tag/v10.34.5)
42
+ needed to start pnpm 12 on macOS and Windows.
43
+
34
44
  The starter includes a notes app, a D1 database, private R2 file storage and a
35
45
  server-side identity helper. Local development uses a synthetic user. Open the
36
46
  local URL printed by `pnpm dev`, then stop that server with Ctrl-C before continuing.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "widefleet-darwin-arm64",
3
- "version": "0.3.3",
3
+ "version": "0.4.0",
4
4
  "description": "Widefleet CLI with its Worker bundler and app starter",
5
5
  "homepage": "https://widefleet.com",
6
6
  "license": "MIT",
package/release.json CHANGED
@@ -1,5 +1,5 @@
1
1
  {
2
2
  "format": 1,
3
- "version": "0.3.3",
3
+ "version": "0.4.0",
4
4
  "esbuild_version": "0.28.2"
5
5
  }
package/starter/README.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # SvelteKit app on Widefleet
2
2
 
3
- This is an independent app project. It needs Node.js 26, pnpm 12.4.2 and an installed Widefleet CLI release. Docker and the Widefleet source repository are not required on the developer machine.
3
+ This is an independent app project. It needs Node.js 22.18 or newer, an existing pnpm 10.34.5 or newer installation and an installed Widefleet CLI release. With pnpm's default version management, the project automatically downloads and uses its pinned pnpm 12.4.2. Docker and the Widefleet source repository are not required on the developer machine.
4
4
 
5
5
  ```sh
6
6
  pnpm install --frozen-lockfile
@@ -0,0 +1,66 @@
1
+ # TanStack Start app on Widefleet
2
+
3
+ This independent React app uses TanStack Start, D1 notes and private R2 photos.
4
+ You need Node.js 22.18 or newer, an existing pnpm 10.34.5 or newer installation,
5
+ and the Widefleet CLI release that generated this project. With pnpm's default
6
+ version management, the project automatically downloads and uses its pinned pnpm
7
+ 12.4.2. Docker and the Widefleet source repository are not required.
8
+
9
+ ```sh
10
+ pnpm install --frozen-lockfile
11
+ pnpm check
12
+ pnpm dev
13
+ ```
14
+
15
+ Open the local URL printed by the development server. The page shows a synthetic
16
+ identity; create a note with a photo to verify local storage. JavaScript is
17
+ required to submit the example form.
18
+
19
+ ## Build and deploy
20
+
21
+ Stop the development server and connect to your company's installation:
22
+
23
+ ```sh
24
+ widefleet login
25
+ pnpm check
26
+ widefleet deploy
27
+ ```
28
+
29
+ The CLI builds the app and deploys the Worker declared in `wrangler.jsonc`. Review
30
+ its `name` and the platform selected by `widefleet config show` before deploying.
31
+ After activation, open the printed app URL and sign in with your company account.
32
+ See [CLI installation](https://widefleet.com/docs/getting-started/installation)
33
+ for setup and login recovery.
34
+
35
+ ## App development
36
+
37
+ Edit `src/routes` and use `context.user` in server functions and server routes
38
+ for the verified company identity. Preserve authentication in `src/server.ts`
39
+ and CSRF protection in `src/start.ts`. Deployed apps cannot use separate cookie
40
+ sessions.
41
+
42
+ Declare resources in `wrangler.jsonc`. Run `pnpm types` after adding routes or
43
+ changing bindings; `.platform` contains generated files. Use `pnpm build` when
44
+ building manually: it generates a single version for browser and server error
45
+ reports. Direct `vite build` exits with a message to use the build script.
46
+
47
+ The example uses `DB` and `FILES`; keep those declarations while using its notes
48
+ and photos. Database and file contents survive code deployments and rollback.
49
+ Use [explicit migrations](https://widefleet.com/docs/guides/migrations) when
50
+ changing an existing schema.
51
+
52
+ The starter captures unexpected server and browser errors. For caught technical
53
+ failures, use `captureError` from `src/lib/server/capture-error.ts` on the server
54
+ or `src/lib/capture-error.ts` in browser code. Keep source maps private and
55
+ preserve the browser's embedded build version.
56
+
57
+ ```sh
58
+ widefleet logs --level error --since 1h --json
59
+ ```
60
+
61
+ Runtime logs require the operator's telemetry services. If the command fails,
62
+ report that failure rather than assuming there are no errors.
63
+
64
+ Next, [publish an isolated preview](https://widefleet.com/docs/guides/deployments)
65
+ or follow [app development](https://widefleet.com/docs/guides/app-development)
66
+ for resources, network permissions and IT connectors.
package/widefleet CHANGED
Binary file