Fix start command in build instructions

[rmoff]

Following the existing instructions I got this:

❯ bun run build
$ bun build --target=node --format=esm --bundle --sourcemap --outdir=build ./src/index.ts ./src/server.ts
Bundled 329 modules in 34ms

  index.js       0.96 MB  (entry point)
  server.js      1.78 MB  (entry point)
  index.js.map   1.82 MB  (source map)
  server.js.map  2.98 MB  (source map)

❯ bun start
error: Script not found "start"

[gemini-code-assist]

Summary of Changes

Hello @rmoff, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses an issue in the build instructions by correcting the command used to start the application. The previous instruction bun start was non-functional, leading to a "Script not found" error. The updated instruction bun run start:http ensures that users can successfully build and run the application as intended.

Highlights

• Build Instructions Correction: Updated the README.md to use bun run start:http instead of bun start for running the application, resolving an error where the start script was not found.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request fixes a broken command in the README.md build instructions. The change from bun start to bun run start:http resolves the error reported. My review includes a suggestion to further improve the instructions by running the compiled server artifact instead of the source file, which aligns better with the 'Build and Run' section's intent and improves clarity for users.

[gemini-code-assist]

Thank you for fixing the broken command. While bun run start:http works, it runs the server from the source TypeScript file. Since the preceding step is bun run build, it's more logical and less confusing for the user to run the compiled JavaScript file that was just created. This makes the 'Build and Run' sequence more intuitive.

Suggested change

	bun run start:http
	bun build/server.js