Skip to content

Type 'Timer' is not assignable to type 'Timeout'. #2355

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Justman100 opened this issue Jun 22, 2024 · 3 comments
Closed

Type 'Timer' is not assignable to type 'Timeout'. #2355

Justman100 opened this issue Jun 22, 2024 · 3 comments
Labels

Comments

@Justman100
Copy link

Justman100 commented Jun 22, 2024

Bug description

Get only this:
grafik

How to reproduce

git init
git pull GitbookIO/gitbook
bun install
bun next build
@Justman100 Justman100 added the bug label Jun 22, 2024
@Justman100
Copy link
Author

@jpreynat

@jpreynat
Copy link
Member

@Justman100 A fresh install works for me.

After looking around quickly, it looks like the Timer type that you got for setTimeout could come from bun's types, while the one I got and that's used at compile time is the @types/node's module one.

Might be good to check that you use the same version of bun as I am, 1.1.17, but otherwise I'm not sure what's wrong.
Just as an additional clue, if the build from scratch was actually failing, our PRs and main branch deployments to Cloudflare Pages would fail too. I'm thus closing the issue and I encourage you to look at your local configuration.

@Justman100
Copy link
Author

After looking around quickly, it looks like the Timer type that you got for setTimeout could come from bun's types, while the one I got and that's used at compile time is the @types/node's module one.

And how do I change that?

Might be good to check that you use the same version of bun as I am, 1.1.17, but otherwise I'm not sure what's wrong. Just as an additional clue, if the build from scratch was actually failing, our PRs and main branch deployments to Cloudflare Pages would fail too. I'm thus closing the issue and I encourage you to look at your local configuration.

Is that a joke? Two minor versions in just 3 days? But no, the latest version has the same error!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants