chore: update package.json scripts for bun and next compatibility

[roderik]

Modified the scripts in package.json to ensure compatibility with the latest bun and next versions, including changes to the build, dev, and start commands. Additionally, adjusted the clean script to enhance file removal processes.

Summary by Sourcery

Improve package.json scripts for bun and Next.js compatibility and tweak global CSS.

Enhancements:

• Set max-width to 100% on #nd-page in global CSS

Build:

• Revise clean script to remove lock files and run bun install
• Add --turbopack flag to next build and dev commands

[gemini-code-assist]

Summary of Changes

Hello @roderik, 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 primarily focuses on enhancing development workflow efficiency and improving UI responsiveness. It updates key build and development scripts to leverage modern tooling features and introduces a minor CSS adjustment to ensure better layout consistency.

Highlights

• Script Updates: The build and dev scripts in package.json have been updated to utilize --turbopack for potentially faster compilation and development.
• UI Styling Adjustment: The #nd-page style in src/app/global.css now includes max-width: 100% to ensure proper rendering across different screen sizes.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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. ↩

[github-actions]

To view in Slack, search for: 1757483933.931329

[sourcery-ai]

Hey there - I've reviewed your changes - here's some feedback:

• The clean script now includes bun install which mixes cleaning with installation—consider splitting these into separate scripts to keep responsibilities clear.
• You’ve added --turbopack flags to build and dev but not start—ensure consistency or confirm that start doesn’t require the flag.
• The max-width:100% on #nd-page may override intended layout constraints; verify this change works across all breakpoints.

Prompt for AI Agents

Please address the comments from this code review:
## Overall Comments
- The clean script now includes bun install which mixes cleaning with installation—consider splitting these into separate scripts to keep responsibilities clear.
- You’ve added --turbopack flags to build and dev but not start—ensure consistency or confirm that start doesn’t require the flag.
- The max-width:100% on #nd-page may override intended layout constraints; verify this change works across all breakpoints.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[gemini-code-assist]

Code Review

This pull request updates the package.json scripts to use Turbopack for both development and production builds, and adds a CSS rule to global.css. While using Turbopack for development is a good performance enhancement, using it for production builds is still considered beta and may lead to instability. I have suggested removing the --turbopack flag from the build script to ensure production stability. The CSS change seems to be a straightforward layout improvement.

[gemini-code-assist]

Using --turbopack for production builds (next build) is currently in beta and may not be stable. It is generally recommended to use experimental features like this for development environments only, to avoid potential issues in production. Consider removing the --turbopack flag from the build script to ensure a stable production build.

Suggested change

	"build": "bun generate-sdk-docs && next build --turbopack",
	"build": "bun generate-sdk-docs && next build",

[dosubot]

Related Documentation

Checked 1 published document(s). No updates required.

^{How did I do? Any feedback?}  

[chatgpt-codex-connector]

Codex Review: Here are some suggestions.

About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you open a pull request for review, mark a draft as ready, or comment "@codex review". If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex fix this CI failure" or "@codex address that feedback".

[chatgpt-codex-connector]

[P1] Use current Next.js flag for Turbopack builds

The build and dev scripts now call next build --turbopack and next dev --turbopack, but the Next 15 CLI bundled in this repo exposes the Turbopack switch as --turbo (the --turbopack alias was removed). When these scripts run, Next exits with “Unknown or unexpected option: --turbopack”, preventing both bun run build and bun run dev from starting at all. Switching the flag to --turbo restores compatibility with Next 15.5.2.

Useful? React with 👍 / 👎.

[dosubot]

Documentation Updates

Checked 1 published document(s). No updates required.

^{How did I do? Any feedback?}