Migrate to domstack-sync

[bcomnes]

Migrate to a modernized domstack sync from browsersync.

[Copilot]

Pull request overview

Replaces the legacy browser-sync integration with @domstack/sync for the dev server and routes build/watch logs through a structured logger created via createLogger. The watch() API gains an onInitialBuild hook so the CLI can render its build tree after watchers are ready and before the dev server starts.

Changes:

• Swap browser-sync for @domstack/sync in production deps (and remove @types/browser-sync); start the dev server via createServer and shut it down via await syncServer.exit().
• Replace console.log/error calls in DomStack with a pino-style logger, exposed/initialized through a new createLogger helper and a logger build option.
• Refactor watch() to register cpx event listeners up front, await Promise.all of watcher readiness, invoke a new onInitialBuild(report) callback, and only then spin up the sync server; update example package.jsons to drop browser-sync/npm-run-all2 in favor of domstack --watch.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
package.json	Adds @domstack/sync@^0.0.4, drops browser-sync and @types/browser-sync.
index.js	Imports @domstack/sync, adds createLogger/wrapPinoLogger exports, swaps console logs for the structured logger, restructures watch() cpx setup, adds onInitialBuild, and replaces browserSyncServer with #syncServer.
lib/builder.js	Documents new optional logger BuildOpts property typed against @domstack/sync.
bin.js	Creates a CLI logger, passes it via opts, moves post-initial-build tree/warning output into the new onInitialBuild callback, and routes quit messages through the logger.
examples/string-layouts/package.json	Replaces split watch:serve/watch:domstack scripts with domstack --watch; removes browser-sync and npm-run-all2 devDeps.
examples/default-layout/package.json	Same example simplification as string-layouts.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[coveralls]

Coverage Report for CI Build 28344270455

Coverage increased (+0.4%) to 92.302%

Details

• Coverage increased (+0.4%) from the base build.
• Patch coverage: 67 uncovered changes across 2 files (130 of 197 lines covered, 65.99%).
• 1 coverage regression across 1 file.

Uncovered Changes

File	Changed	Covered	%
lib/logger.js	80	43	53.75%
index.js	115	85	73.91%
Total (3 files)	197	130	65.99%

Coverage Regressions

1 previously-covered line in 1 file lost coverage.

File	Lines Losing Coverage	Coverage
index.js	1	82.17%

---

Coverage Stats

Relevant Lines:	4292
Covered Lines:	4041
Line Coverage:	94.15%
Relevant Branches:	709
Covered Branches:	575
Branch Coverage:	81.1%
Branches in Coverage %:	Yes
Coverage Strength:	73.98 hits per line

---

💛 - Coveralls

[Copilot]

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated no new comments.

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm @fastify/middie is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/@domstack/sync@0.0.5 → npm/@fastify/middie@9.3.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@fastify/middie@9.3.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[bcomnes]

Spotted some issues.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​domstack/​sync@​0.0.5
	npm/​pino-pretty@​13.1.3
	npm/​pino@​9.14.0

View full report

[bcomnes]

Follow-up: simplified lib/logger.js so the production logger no longer accepts or wraps custom streams. createDomStackLogger() now just creates the app logger and lets pino-pretty handle stdout. The watch test uses its own local logger double instead of adding stream plumbing to production code.

[bcomnes]

OK code actually looks okay! This just needs one more round interactive testing.

[bcomnes]

Looks good.