Please make sure you have searched for information in the following guides.

• Search the issues already opened: https://github.com/GoogleCloudPlatform/google-cloud-node/issues
• Search StackOverflow: http://stackoverflow.com/questions/tagged/google-cloud-platform+node.js
• Check our Troubleshooting guide: https://github.com/googleapis/google-cloud-node/blob/main/docs/troubleshooting.md
• Check our FAQ: https://github.com/googleapis/google-cloud-node/blob/main/docs/faq.md
• Check our libraries HOW-TO: https://github.com/googleapis/gax-nodejs/blob/main/client-libraries.md
• Check out our authentication guide: https://github.com/googleapis/google-auth-library-nodejs
• Check out handwritten samples for many of our APIs: https://github.com/GoogleCloudPlatform/nodejs-docs-samples

A screenshot that you have tested with "Try this API".

Has anyone encountered this before?

Repo:

import { Spanner } from "@google-cloud/spanner";

const spanner = new Spanner({
    projectId: "id",
});

console.log("Spanner initialized");

run this file and this will throw that error.

bun version: 1.2.19
google-cloud/spanner: 8.0.0

Link to the code that reproduces this issue. A link to a public Github Repository or gist with a minimal reproduction.

https://gist.github.com/plgrazon/5a6c305520837d07c4456093e1c08262

A step-by-step description of how to reproduce the issue, based on the linked reproduction.

1. Create a file with this implemenation
2. Run the file with: bun [file]

A clear and concise description of what the bug is, and what you expected to happen.

Has anyone encountered this before?

Error:
[bun] Warning: async_hooks.createHook is not implemented in Bun. Hooks can still be created but will never be called.

Repo:

import { Spanner } from "@google-cloud/spanner";

const spanner = new Spanner({
    projectId: "id"
});

console.log("Spanner initialized");

run this file and this will throw that error.

bun version: 1.2.19
google-cloud/spanner: 8.0.0

A clear and concise description WHY you expect this behavior, i.e., was it a recent change, there is documentation that points to this behavior, etc. **

This error shouldn't appear, query seems to be working fine though