@buildkitgg/dev-domains 0.0.2 → 0.1.1

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/CHANGELOG.md CHANGED
@@ -1,12 +1,44 @@
1
- # Changelog
1
+ # Change Log - @buildkitgg/dev-domains
2
+
3
+ <!-- This log was last generated on Thu, 22 Oct 2026 20:48:42 GMT and should not be manually modified. -->
4
+
5
+ <!-- Start content -->
6
+
7
+ ## 0.1.1
8
+
9
+ Thu, 22 Oct 2026 20:48:42 GMT
10
+
11
+ ### Patches
12
+
13
+ - Refresh dependencies and verify compatibility with React 19.3 and Vitest 5. (ajcraswell@gmail.com)
14
+ - Update repository metadata for packages grouped by core, React, UI integrations, and tooling. (ajcraswell@gmail.com)
15
+
16
+ ## 0.1.0
17
+
18
+ ### Changed defaults
19
+
20
+ - App discovery uses the package's `dev` script. Other script names remain supported through explicit `script`
21
+ configuration, but are no longer automatically preferred or selected.
22
+ - Suggested E2E endpoints no longer set `DEV_DOMAINS_OUTPUT_DIR`. Configure framework output and cache isolation in the
23
+ application. Existing explicit `env` values remain supported.
24
+
25
+ ### Fixes
26
+
27
+ - A dedicated test endpoint added in the wizard keeps the selected app command, including custom servers without a `dev`
28
+ script.
29
+ - Installation, examples, and setup guidance use public commands and neutral project names. Contributor documentation
30
+ holds runtime implementation details.
31
+
32
+ Existing saved configurations remain valid. This pre-1.0 minor release makes the discovery changes explicit; projects
33
+ that relied on the previous inferred values should save their intended scripts and environment settings in a config.
2
34
 
3
35
  ## 0.0.2
4
36
 
5
37
  - Allow projects with different domains to share Portless without endpoint-name collisions. For example,
6
- `local.copacker.ai` and `local.spawnkit.cloud` now remain separate routes on one proxy.
38
+ `local.example.com` and `local.example.org` now remain separate routes on one proxy.
7
39
  - Preserve explicit `proxy.domains` aliases and reject occupied complete hostnames without takeover.
8
- - Reserve an OS-assigned port through route registration, retry bounded bind failures, and clean only owned routes.
9
- - Execute framework commands directly with argument arrays on Windows, Linux, and macOS.
40
+ - Assign backend ports automatically and leave other projects running when a server stops.
41
+ - Run server commands consistently on Windows, Linux, and macOS.
10
42
 
11
43
  Existing configuration files and public APIs remain compatible. Shared projects still need the same proxy port and TLS
12
44
  mode, and custom domains must resolve locally. No DNS or provider settings are changed automatically.
package/README.md CHANGED
@@ -4,8 +4,8 @@ Stable local URLs for your app, Storybook, and end-to-end test servers, across r
4
4
 
5
5
  `@buildkitgg/dev-domains` gives each server a predictable hostname and runs it through
6
6
  [Portless](https://github.com/vercel-labs/portless). You can open `https://shop.localhost` in your primary checkout and
7
- `https://shop-fix-login.localhost` in a worktree, while Portless assigns the underlying ports. A configuration file lets
8
- you choose your own names, use a real domain, describe authentication callbacks, and expose selected webhook routes.
7
+ `https://shop-fix-login.localhost` in a worktree, with ports assigned automatically. A configuration file lets you
8
+ choose your own names, use a real domain, describe authentication callbacks, and expose selected webhook routes.
9
9
 
10
10
  Requires Node.js 24 or later. Supports Windows, macOS, and Linux.
11
11
 
@@ -30,7 +30,6 @@ Requires Node.js 24 or later. Supports Windows, macOS, and Linux.
30
30
  - [CI usage](#ci-usage)
31
31
  - [Command reference](#command-reference)
32
32
  - [Troubleshooting](#troubleshooting)
33
- - [Contributing and license](#contributing-and-license)
34
33
 
35
34
  ## Motivation and philosophy
36
35
 
@@ -48,8 +47,8 @@ The package follows a few principles:
48
47
  configuration when your project needs different names or commands.
49
48
  - **Readable checkout names.** Identify linked worktrees by their folder names. The primary checkout has no `main`
50
49
  label, and hostnames do not acquire random hashes.
51
- - **Reuse Portless.** Portless owns the proxy, certificates, and shared route registry. This package adds project
52
- conventions and integrations around it.
50
+ - **A convenience helper around Portless.** [Portless](https://github.com/vercel-labs/portless) provides local routing
51
+ and HTTPS. This package adds tool detection, typed configuration, and consistent domains across apps and worktrees.
53
52
  - **Report conflicts.** A running endpoint keeps its hostname. Another process must choose a different name instead of
54
53
  taking over the route.
55
54
  - **Keep application choices with the application.** Authentication providers, cloud resources, DNS administration, and
@@ -143,39 +142,40 @@ When no configuration file is found, these conventions determine the candidates:
143
142
  | Project name | Root `package.json` name, otherwise the root folder name, normalized as described below |
144
143
  | Package manager | Root `packageManager`, then `devEngines.packageManager`, then lockfiles, then installation metadata; npm if none is found |
145
144
  | Workspace packages | Root plus declared `pnpm-workspace.yaml` packages or `package.json` workspaces; without declarations, packages found recursively below the root |
146
- | App server | First eligible script in this order: `dev:app`, `dev:raw`, `dev` |
145
+ | App server | The package's `dev` script, when it starts one server; other script names require explicit configuration |
147
146
  | Storybook server | A script containing `storybook dev`; otherwise a discovered `.storybook/main.*` config |
148
147
  | Playwright candidate | A `playwright.config.*` file, an `@playwright/test` dependency, or a `playwright test` script, together with an app dev script in the same package |
149
148
  | Framework | Recognized simple Next.js, Vite, and Storybook commands receive framework-specific flags; other commands are `custom` |
150
149
  | Local proxy | HTTPS on port 443, suffix `localhost`, hosts synchronization enabled |
151
150
  | Auth and public access | No callback paths or tunnels are inferred |
152
151
 
153
- Package-manager detection uses
154
- [`package-manager-detector`](https://github.com/antfu-collective/package-manager-detector). It stays at the selected
155
- project root instead of inheriting a manager from an unrelated parent folder. A declaration takes precedence over stale
156
- lockfiles. Conflicting lockfiles without a declaration require you to choose a manager in `package.json` or an explicit
157
- dev-domains config.
152
+ Package-manager detection stays at the selected project root. A declaration takes precedence over stale lockfiles.
153
+ Conflicting lockfiles without a declaration require you to choose a manager in `package.json` or an explicit config.
158
154
 
159
155
  Scripts that invoke `dev-domains`, `portless`, `turbo`, `run-p`, or `concurrently` are excluded from detection. Point
160
156
  configuration at the underlying server script when an aggregate or wrapper command is involved. A `playwright test`
161
157
  script is never used as the app server.
162
158
 
159
+ There is no universally required development script name. `dev` is the default convention; scripts with any other name
160
+ work through an explicit `script` setting. Detection does not guess whether `start`, `serve`, or a custom script is a
161
+ development server, production server, or build task.
162
+
163
163
  ### Storybook and Playwright discovery
164
164
 
165
- One read-only directory walk finds both `.storybook/main.*` and `playwright.config.*`. It recognizes `ts`, `mts`, `cts`,
166
- `js`, `mjs`, `cjs`, `tsx`, and `jsx` filenames. Configs belong to their nearest package, including nested paths such as
165
+ Discovery finds both `.storybook/main.*` and `playwright.config.*`. It recognizes `ts`, `mts`, `cts`, `js`, `mjs`,
166
+ `cjs`, `tsx`, and `jsx` filenames. Configs belong to their nearest package, including nested paths such as
167
167
  `tests/playwright.config.ts`. Tool configuration files are located without being imported or executed.
168
168
 
169
- The walk honors workspace exclusions and skips symlinks, hidden directories other than `.storybook`, `node_modules`,
170
- `dist`, `build`, `out`, `coverage`, `storybook-static`, `playwright-report`, and `test-results`. It stops with an error
171
- above 1,000 packages or 10,000 visited directories; use explicit configuration for larger or unusual layouts.
169
+ Discovery honors workspace exclusions and skips dependencies, generated output, symlinks, and hidden directories other
170
+ than `.storybook`. Use explicit configuration for unusual layouts or when discovery reports that a project is too large.
172
171
 
173
172
  For Storybook, a dev script takes precedence over config-file discovery. With one config and no dev script, the
174
173
  candidate runs the installed `storybook dev --config-dir <directory>` binary. Nothing is downloaded. Multiple dev
175
174
  scripts, or multiple configs without a clear dev script, require explicit configuration. An empty `.storybook` folder or
176
175
  a Storybook dependency alone does not establish a runnable server.
177
176
 
178
- For Playwright, the candidate starts a separate copy of the app dev server. It is named `app-e2e`, or
177
+ Finding Playwright does not reveal which server your tests need. The suggested endpoint starts a separate copy of the
178
+ package's `dev` server; it does not read Playwright's `webServer` configuration. It is named `app-e2e`, or
179
179
  `<package>-app-e2e` in a workspace. Select it explicitly in the wizard or run it by name when using zero configuration.
180
180
  `init --yes` omits it. A dependency on the `playwright` browser library alone does not imply an E2E test setup. Separate
181
181
  test-only packages and cross-package server relationships need explicit configuration. See [Playwright](#playwright)
@@ -230,7 +230,7 @@ export default defineConfig({
230
230
  endpoints: {
231
231
  app: {
232
232
  cwd: "apps/web",
233
- script: "dev:raw",
233
+ command: ["next", "dev"],
234
234
  framework: "next",
235
235
  primaryName: "local",
236
236
  name: "{worktree}.local"
@@ -347,10 +347,10 @@ A saved configuration is complete: detected endpoints are not merged into it. In
347
347
  in a saved config defaults to **npm**, while zero-config discovery detects the manager. Specify your manager when
348
348
  authoring a config for pnpm, Yarn, or Bun.
349
349
 
350
- Configuration loading uses c12 with home configuration, implicit `.env` loading, package.json config, remote extensions,
351
- and environment-specific merging disabled. Your framework may still load its own environment files. JavaScript and
352
- TypeScript configs execute as code when loaded; use configs from repositories you trust. The `detect` command always
353
- inspects project conventions without loading a dev-domains config.
350
+ Only the selected configuration file is loaded. The CLI does not load `.env` files, user-wide settings, remote
351
+ configuration, or environment-specific overrides. Your framework may still load its own environment files. JavaScript
352
+ and TypeScript configs execute as code when loaded; use configs from repositories you trust. `detect` inspects project
353
+ conventions without loading a dev-domains config.
354
354
 
355
355
  ### JSON editor support
356
356
 
@@ -498,9 +498,9 @@ Use `framework: "custom"` for compound shell scripts or commands that cannot acc
498
498
  automatically for compound scripts. In a saved config, choose the appropriate framework yourself. `kind` does not select
499
499
  it for you.
500
500
 
501
- Keep the underlying server script free of another `dev-domains` or Portless invocation. For example, a package can use
502
- `"dev": "npx @buildkitgg/dev-domains run app"` together with `"dev:raw": "vite"`, while the endpoint references
503
- `script: "dev:raw"`. Configuring `script: "dev"` in that example would recurse and is rejected.
501
+ If you replace your `dev` script with `npx @buildkitgg/dev-domains run app`, configure the endpoint with the server
502
+ command directly, such as `command: ["vite"]` and `framework: "vite"`. Pointing that endpoint back to `script: "dev"`
503
+ would start the CLI again and is rejected. You do not need a second package script with a special name.
504
504
 
505
505
  Your framework still controls allowed hosts, development origins, and output directories. Add your generated hostnames
506
506
  to its configuration where required. When a server exits, its exit code is propagated. Custom servers must fail on a
@@ -516,17 +516,16 @@ separate server, configure a dedicated endpoint:
516
516
  "app-e2e": {
517
517
  kind: "e2e",
518
518
  cwd: "apps/web",
519
- script: "dev:raw",
520
- framework: "next",
521
- env: { DEV_DOMAINS_OUTPUT_DIR: ".dev-domains/app-e2e" }
519
+ command: ["vite"],
520
+ framework: "vite"
522
521
  }
523
522
  ```
524
523
 
525
524
  Then use the helper in `playwright.config.ts`:
526
525
 
527
526
  ```ts
528
- import { defineConfig } from "@playwright/test"
529
527
  import { playwrightServer } from "@buildkitgg/dev-domains/playwright"
528
+ import { defineConfig } from "@playwright/test"
530
529
 
531
530
  export default defineConfig({
532
531
  ...(await playwrightServer("app-e2e")),
@@ -543,10 +542,10 @@ dev-domains config can be found.
543
542
  The endpoint's script must start a server, not run `playwright test`. The helper does not install Playwright or edit its
544
543
  configuration. Run `npx @buildkitgg/dev-domains setup` before the test run on a development machine.
545
544
 
546
- A dedicated endpoint gets a separate hostname and port, but you must also isolate build output when the framework
547
- requires it. Detection and the wizard set `DEV_DOMAINS_OUTPUT_DIR` for E2E candidates. The framework must consume that
548
- variable; for example, a Next.js config can set `distDir: process.env.DEV_DOMAINS_OUTPUT_DIR || ".next"`. Databases,
549
- storage, and credentials are still shared unless you configure them separately.
545
+ A dedicated endpoint gets a separate hostname and port. Configure separate build output or caches when your framework
546
+ requires them; this package does not change those settings or assign a framework output directory. Tests that need a
547
+ production build, another package, or a remote deployment need an explicit server configuration. Databases, storage, and
548
+ credentials remain shared unless you configure them separately.
550
549
 
551
550
  ## Node.js tooling
552
551
 
@@ -562,8 +561,8 @@ process.env.APP_URL = app.origin
562
561
  `getEndpoint(service, cwd?)` returns a promise containing `service`, `hostname`, `origin`, `callbacks` (resolved auth
563
562
  URLs), and `cwd` (the server's absolute working directory). It uses the CLI's configuration discovery and worktree
564
563
  naming rules; `cwd` defaults to `process.cwd()`. An unknown endpoint throws. The exported `EndpointInfo` type describes
565
- the result. This Node.js-only helper can execute trusted local configuration files, just like the CLI. It does not
566
- allocate a port, start the proxy, or register a route.
564
+ the result. This Node.js-only helper can execute trusted local configuration files, just like the CLI. It does not start
565
+ servers or change networking settings.
567
566
 
568
567
  ## Authentication callbacks
569
568
 
@@ -615,12 +614,11 @@ No separate webhook subdomain is required. A quick tunnel URL may change after r
615
614
  configure a stable tunnel with your provider and optionally record its HTTPS origin in `tunnel.publicUrl`. That property
616
615
  reports an existing address; it does not reserve a domain or configure the tunnel command.
617
616
 
618
- The tunnel targets a restricted gateway that holds an OS-assigned loopback port open. It forwards only POST requests
619
- whose paths exactly match `tunnel.paths`. Query strings, raw request bytes, and signature headers are preserved;
620
- hop-by-hop headers and the inbound `Forwarded`, `X-Forwarded-For`, and `X-Forwarded-Host` headers are stripped. Request
621
- bodies are limited to 1 MiB, upstream requests time out after 15 seconds, and payloads are not logged or stored. Your
622
- application must validate provider signatures. Providers that require a GET verification challenge need a different
623
- ingress arrangement; this gateway is POST-only.
617
+ The tunnel accepts only POST requests whose paths exactly match `tunnel.paths`. Query strings, raw request bytes, and
618
+ signature headers are preserved; hop-by-hop headers and the inbound `Forwarded`, `X-Forwarded-For`, and
619
+ `X-Forwarded-Host` headers are stripped. Request bodies are limited to 1 MiB, upstream requests time out after 15
620
+ seconds, and payloads are not logged or stored. Your application must validate provider signatures. Providers that
621
+ require a GET verification challenge need a different ingress arrangement; this gateway is POST-only.
624
622
 
625
623
  Install and authenticate the tunnel executable separately. It runs from the configuration root and inherits the shell
626
624
  environment, rather than the endpoint's server `env` overrides. Keep credentials in the provider's login store or
@@ -643,23 +641,19 @@ proxy: {
643
641
  }
644
642
  ```
645
643
 
646
- Each project registers complete hostnames in Portless's shared route registry. Projects can use different domains
647
- without coordinating a suffix list: `local.copacker.ai` and `local.spawnkit.cloud` can run together on the same proxy.
644
+ Projects can use different domains: `local.example.com` and `local.example.org` can run together on the same proxy.
648
645
  Leave `proxy.domains` unset unless this project's endpoints should have additional aliases. An explicit list registers
649
- each endpoint under those suffixes only; `domain` selects its canonical origin. This preserves existing alias configs. A
650
- collision means the **complete hostname** is occupied, not just the endpoint name.
646
+ each endpoint under those suffixes only; `domain` selects its canonical origin. A collision means the **complete
647
+ hostname** is occupied, not just the endpoint name.
651
648
 
652
- Projects sharing one proxy must agree on its port and TLS settings. Buildkit reuses a compatible proxy without changing
653
- its startup suffixes or restarting it. DNS must resolve every custom hostname to loopback; either use Portless's hosts
654
- synchronization or configure DNS yourself. If the existing proxy was started with hosts synchronization disabled,
655
- `syncHosts: true` cannot change that running process. Coordinate proxy configuration or configure DNS separately.
656
- `npx @buildkitgg/dev-domains doctor` helps diagnose the current state.
649
+ Projects sharing one proxy must agree on its port and TLS settings. Starting an endpoint leaves other servers running.
650
+ DNS must resolve every custom hostname to loopback; either use Portless's hosts synchronization or configure DNS
651
+ yourself. If the existing proxy was started with hosts synchronization disabled, `syncHosts: true` cannot change that
652
+ running process. Coordinate proxy configuration or configure DNS separately. `npx @buildkitgg/dev-domains doctor` helps
653
+ diagnose the current state.
657
654
 
658
- Buildkit holds an OS-assigned loopback port while registering the route, then releases the socket immediately before
659
- starting the server. Other Buildkit launchers avoid ports in the shared registry, including servers still starting. Most
660
- framework CLIs cannot inherit the reserved socket, so unrelated programs can still race that final handoff. Buildkit
661
- makes at most three attempts, retrying only an explicit `EADDRINUSE` or address-in-use failure. Make startup safe to
662
- repeat. A hostname collision never triggers a forced route takeover.
655
+ Backend ports are assigned automatically. Startup may be retried after a port conflict, so server commands should be
656
+ safe to repeat. A running server keeps its hostname; choose another name if the CLI reports a collision.
663
657
 
664
658
  ## CI usage
665
659
 
@@ -697,16 +691,17 @@ first.
697
691
  `--cwd` defaults to the current directory. `--config` is a file path relative to `--cwd`. Use `--help` on a command for
698
692
  its options. `run` and `tunnel` require an endpoint name in noninteractive sessions when more than one candidate exists.
699
693
 
700
- The CLI never rewrites package scripts. It propagates server exit codes and cleans up its own routes when the server
701
- stops. The shared proxy is left running. After a hard crash, Portless handles stale routes during subsequent operation.
702
- `PORTLESS_STATE_DIR` can select a separate state directory; most consumers should keep the default shared state.
694
+ The CLI never rewrites package scripts. It propagates server exit codes and releases the endpoint's hostname when the
695
+ server stops normally. The shared proxy stays available for other servers. After a forced termination, check `status`
696
+ and stop any remaining server process you own before restarting it. `PORTLESS_STATE_DIR` can select a separate state
697
+ directory; most consumers should keep the default shared state.
703
698
 
704
699
  ## Troubleshooting
705
700
 
706
701
  | Symptom | What to check |
707
702
  | ---------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
708
703
  | No endpoints were detected | Run `detect`; check the app script conventions or add an explicit `command` / `script` endpoint |
709
- | A wrapped script is rejected | Reference the underlying server script, such as `dev:raw`, instead of a script invoking dev-domains or Portless |
704
+ | A wrapped script is rejected | Set `command` to the server executable, or reference a script that starts the server directly |
710
705
  | An endpoint name is ambiguous | Use `urls` for configured names or `detect` for discovered names, then pass one to `run` |
711
706
  | Multiple configs or Storybook candidates were found | Keep one dev-domains config per directory; select the intended Storybook script or config directory explicitly |
712
707
  | The wrong package manager is used | In a saved config, set `packageManager`; during discovery, check the root declaration and conflicting lockfiles |
@@ -714,15 +709,6 @@ stops. The shared proxy is left running. After a hard crash, Portless handles st
714
709
  | The proxy has different settings | Align port and TLS settings with the existing shared proxy before restarting your endpoint |
715
710
  | The hostname does not resolve or HTTPS is untrusted | Run `doctor`; check loopback DNS or hosts synchronization and complete Portless certificate setup |
716
711
  | The framework rejects the hostname | Configure its allowed hosts or development origins for your generated domains |
717
- | App and E2E servers conflict despite different ports | Configure separate framework build/output directories; verify the app consumes `DEV_DOMAINS_OUTPUT_DIR` |
712
+ | App and E2E servers conflict despite different ports | Configure separate framework build/output directories or caches |
718
713
  | A webhook returns 404 | Confirm it is a POST request to an exact allowed path; GET verification challenges are not supported by this gateway |
719
714
  | A webhook cannot reach the app | Start the target endpoint first, verify the provider's current public URL, and check the tunnel process |
720
-
721
- ## Contributing and license
722
-
723
- See the
724
- [architecture and testing guide](https://github.com/AndrewCraswell/buildkit/blob/main/packages/dev-domains/docs/README.md)
725
- and [contributor guide](https://github.com/AndrewCraswell/buildkit/blob/main/CONTRIBUTING.md) for development details.
726
-
727
- [MIT licensed](https://github.com/AndrewCraswell/buildkit/blob/main/LICENSE). Part of Buildkit, whose domain is
728
- [buildkit.gg](https://buildkit.gg). No Buildkit hosted service is required to use this package.
package/dist/cli/init.js CHANGED
@@ -76,7 +76,7 @@ export async function initialize(cwd, options) {
76
76
  endpoint.primaryName = await ask(`Primary checkout name for ${key} ({project}, {service} supported)`, endpoint.primaryName || "{project}-{service}");
77
77
  endpoint.name = await ask(`Worktree name for ${key} ({project}, {worktree}, {service} supported)`, endpoint.name || "{project}-{worktree}-{service}");
78
78
  if (endpoint.kind === "e2e") {
79
- prompts.note("This starts a separate copy of the app server. For frameworks with build locks, use DEV_DOMAINS_OUTPUT_DIR for a separate output directory. Configure Playwright to use this endpoint; databases remain shared.", "Test server isolation");
79
+ prompts.note("This starts a separate copy of the app server. Configure Playwright to use its URL and isolate framework output and application resources as needed.", "Test server isolation");
80
80
  }
81
81
  if (endpoint.kind === "storybook" || endpoint.kind === "e2e") {
82
82
  continue;
@@ -97,7 +97,6 @@ export async function initialize(cwd, options) {
97
97
  .map((value) => value.trim());
98
98
  }
99
99
  if (capabilities.includes("e2e")) {
100
- const script = await ask("Script for the dedicated test server", endpoint.script || "dev");
101
100
  const name = `${key}-e2e`;
102
101
  if (candidate.endpoints[name]) {
103
102
  throw new Error(`Endpoint ${name} already exists`);
@@ -105,14 +104,11 @@ export async function initialize(cwd, options) {
105
104
  additions[name] = {
106
105
  ...endpoint,
107
106
  kind: "e2e",
108
- command: undefined,
109
- script,
110
107
  primaryName: "{project}-{service}",
111
108
  name: "{project}-{worktree}-{service}",
112
- auth: [],
113
- env: { DEV_DOMAINS_OUTPUT_DIR: `.dev-domains/${name}` }
109
+ auth: []
114
110
  };
115
- prompts.note("For frameworks with build locks, configure the test server to use DEV_DOMAINS_OUTPUT_DIR as a separate output directory. Databases remain shared.", "Test server isolation");
111
+ prompts.note("The test endpoint uses the same server command. Edit its configuration if tests need a different command, build output, or application resources.", "Test server isolation");
116
112
  }
117
113
  if (capabilities.includes("webhooks")) {
118
114
  prompts.note("Enter a tunnel command that uses {url} for its target. Credentials stay in the provider's environment or login store. Exposure starts only with dev-domains tunnel.", "Public webhook access");
@@ -140,9 +136,9 @@ export async function initialize(cwd, options) {
140
136
  }
141
137
  const file = await saveConfig(identity.root, candidate);
142
138
  if (options.yes) {
143
- text(`Saved ${file}\nNext: dev-domains setup, then dev-domains run <endpoint>`);
139
+ text(`Saved ${file}\nNext: npx @buildkitgg/dev-domains setup, then npx @buildkitgg/dev-domains run <endpoint>`);
144
140
  }
145
141
  else {
146
- prompts.outro(`Saved ${file}\nNext: dev-domains setup, then dev-domains run <endpoint>`);
142
+ prompts.outro(`Saved ${file}\nNext: npx @buildkitgg/dev-domains setup, then npx @buildkitgg/dev-domains run <endpoint>`);
147
143
  }
148
144
  }
@@ -58,9 +58,7 @@ export async function detectConfig(root) {
58
58
  ...endpoint
59
59
  };
60
60
  };
61
- const dev = ["dev:app", "dev:raw", "dev"]
62
- .map((name) => scripts.find(([script, source]) => script === name && !storybookDev.test(source) && !playwrightTest.test(source)))
63
- .find((entry) => entry !== undefined);
61
+ const dev = scripts.find(([script, source]) => script === "dev" && !storybookDev.test(source) && !playwrightTest.test(source));
64
62
  if (dev) {
65
63
  const [script, source] = dev;
66
64
  add("app", { kind: "app", script, framework: frameworkFor(source) });
@@ -92,8 +90,7 @@ export async function detectConfig(root) {
92
90
  add("app-e2e", {
93
91
  kind: "e2e",
94
92
  script: dev[0],
95
- framework: frameworkFor(dev[1]),
96
- env: { DEV_DOMAINS_OUTPUT_DIR: `.dev-domains/${prefix}app-e2e` }
93
+ framework: frameworkFor(dev[1])
97
94
  });
98
95
  }
99
96
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@buildkitgg/dev-domains",
3
- "version": "0.0.2",
3
+ "version": "0.1.1",
4
4
  "publishConfig": {
5
5
  "access": "public"
6
6
  },
@@ -20,9 +20,9 @@
20
20
  "@repo/typescript-config": "0.0.0",
21
21
  "@types/cross-spawn": "^6.0.6",
22
22
  "@types/node": "24.13.2",
23
- "@vitest/coverage-v8": "4.1.11",
24
- "typescript": "7.0.1-rc",
25
- "vitest": "4.1.11"
23
+ "@vitest/coverage-v8": "5.0.5",
24
+ "typescript": "7.0.2",
25
+ "vitest": "5.0.5"
26
26
  },
27
27
  "type": "module",
28
28
  "engines": {
@@ -55,7 +55,7 @@
55
55
  "repository": {
56
56
  "type": "git",
57
57
  "url": "https://github.com/AndrewCraswell/buildkit.git",
58
- "directory": "packages/dev-domains"
58
+ "directory": "packages/tooling/dev-domains"
59
59
  },
60
60
  "scripts": {
61
61
  "build": "tsc -p tsconfig.build.json",