Make @drfed/web package bundles settings

[dodok8]

Summary

Closes #116

• Add output to files field in package.json
• Add prepack stage to include graphql schema
• Add --backend-url cli arguments set backend sever

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: d689246e-f729-4049-b5b9-d40027f07cb8

---

📥 Commits

Reviewing files that changed from the base of the PR and between 8a155cd and 4c1ceb4.

---

📒 Files selected for processing (3)

• packages/web/README.md
• packages/web/package.json
• packages/web/src/RelayEnvironment.ts

---

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

---

---

📝 Walkthrough

Walkthrough

The web package now starts and publishes its built server. The GraphQL client uses VITE_BACKEND_URL in development and accepts --backend-url otherwise. The README documents how to run the built server.

Changes

Built web server

Layer / File(s)	Summary
Build and publish the server packages/web/package.json	The start script launches the generated server. A prepack script builds the package, which includes .output/ in published files and sets public access.
Configure the GraphQL backend packages/web/src/RelayEnvironment.ts, packages/web/README.md	In development, fetchGraphQL uses VITE_BACKEND_URL. Otherwise, it reads --backend-url and throws an error if the URL is missing. The README shows how to pass the option and configure HOST and PORT.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Feature

Suggested reviewers: sij411

---

Merge Risk: ⚪ Minimal · up to 4c1ce

No confirmed issue blocks merging. The build prerequisite is present; browser behavior for the backend URL remains unverified.

Pre-merge checks | 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check		The title identifies changes to the @drfed/web package bundle settings. It is related to the package publishing and runtime configuration changes, although the wording is awkward.
Description check		The description directly summarizes the package files, prepack stage, and --backend-url argument changes.
Linked Issues check		Issue #116 requires an npm publish path and a build path for self-hosted delivery. packages/web/package.json keeps the build script, adds prepack with mise run build, and publishes .output/.…
Out of Scope Changes check		The changes stay within Issue #116. The package metadata, prepack build, packaged .output/ directory, server start command, backend URL option, and related README instructions all support publishing…
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1…

---

✨ Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

---

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

---

_{Comment @coderabbitai help to get the list of available commands.}