bug_report.md 1.8 KB


name: Bug report about: If you've already confirmed something is broken within the gill sdk itself, create a bug report. title: "[BUG] " labels: ""

assignees: ""

Which gill sdk packages are you having issues with?

For example: gill, @gillsdk/react

What versions of these packages are you using?

For example: v0.11.0

What build tool (or framework if it abstracts the build tool) are you using?

For example: Next.js 15.1.7, Vite 6.1.0

What version of NodeJS (or other server runtime) are you using?

For example: NodeJS v20.0.0, Bun v1.2.1

What package manager (and version) are you using?

For example: pnpm v9.1.0, npm v11.4.2

What browser are you using?

For example: Chrome, Brave, Safari, or N/A

What operating system are you using?

For example: Ubuntu, PopOS, Fedora, MacOS, Windows, etc

Reproduction URL

A public GitHub repo that includes a minimal reproduction of the bug. Please do not link to your actual project, what we need instead is a minimal reproduction in a fresh project without any unnecessary code. This means it doesn't matter if your real project is private/confidential, since we want a link to a separate, isolated reproduction anyways.

A reproduction is required when filing a bug report — any bug report opened without a reproduction will be closed and you'll be asked to create a new issue that includes a reproduction. We're a small team and we can't keep up with the volume of issues we receive if we need to reproduce each issue from scratch ourselves.

Describe your issue

Describe the problem you're seeing, any important steps to reproduce and what behavior you expect instead.