feat: bun related docs (@stonega)

[MasedMSD]

Originally PR was created by @stonega, but it looks like he's not going to continue with this PR. So, I think we should mention Bun as a possible way to work with a bot, even though Bun has a large number of issues. Also Bun finally supports conversations plugin and a decent part of Russian language chat users use it for their projects.

I made some changes and added Bun mentions to the hosting files documentation

[github-actions]

🚀 Deployed on https://67980dfb6082f8b0bcf9d580--grammy.netlify.app

[MasedMSD]

Should we leave index.ts or should we tell the user to create a bot.ts file each time in order for the NodeJS and Deno examples to be the same?

[KnorpelSenf]

I have now wasted more time on this than I ever wanted, maybe I'll get back to this in a week or so

[KnorpelSenf]

The bottom line of this is still that whatever we do with the tutorial, the output must look exactly like

website/site/docs/guide/getting-started.md

Lines 56 to 66 in 53c1efe

	Create a new empty text file, e.g. called `bot.ts`.
	Your folder structure should now look like this:
	```asciiart:no-line-numbers
	.
	├── bot.ts
	├── node_modules/
	├── package.json
	├── package-lock.json
	└── tsconfig.json
	```

and the file contents need to be the same, too. I still do not really care how that is achieved, the point is that as long as the bun guide does not lead to the correct setup, then this cannot be merged.

[MasedMSD]

I'll get into this page in more detail tomorrow

[KnorpelSenf]

Remember to merge main in order to fix CI

[KnorpelSenf]

Scratch that, it already happened

[KnorpelSenf]

I even did it myself *facepalm*

[KnorpelSenf]

This still does not create the same TS config as tsc --init if I understand this correctly

[MasedMSD]

Unfortunately we can't fix it. We will have to ask the user to change it manually every time.
But I don't understand the point of this, because everything works with the current tsconfig O.O

[KnorpelSenf]

Yeah but I don't want to go through all the code examples and make sure that they compile even with the non-standard TS config that bun introduces. It can be fixed very easily by running tsc --init in the getting started guide.

[KnorpelSenf]

Is that in any way related to the current pull request?

[MasedMSD]

I mean that we should have some kind of tests to make sure that the bot and the code work. For example, as for the situation now, when we can't be sure that bun will pass all type-checks

[KnorpelSenf]

That's why you have to test it, or adjust the TS config. But I'm beginning to repeat myself a little

[winstxnhdw]

I mean that we should have some kind of tests to make sure that the bot and the code work. For example, as for the situation now, when we can't be sure that bun will pass all type-checks

It’ll be hard to write integration tests for Bun and grammY because the existing test suite is in Deno. We’d have to spend a lot of time instrumenting some Docker CI test just specifically for Bun, and I am not sure if it’s worth the effort.

[KnorpelSenf]

There's no need to actually run any tests, why do you think this? I can't follow

[MasedMSD]

@KnorpelSenf still confused. We don't gonna use this?

[KnorpelSenf]

I don't have strong opinions on what exactly you're gonna do. I just need you to make sure that the code examples are correct. It doesn't matter to me if you achieve this by making people use the setup that is known to work, or if you want to test all present and future code snippets against a new setup.

[MasedMSD]

What I mean is that this command generates the typescript config that we use in all the examples. I think we should add Bun, but if there are any problems (which I'm not sure about at all, Bun is quite stable) we should deal with them as they come up.

[KnorpelSenf]

So is there still a question? If yes then I don't understand it

[MasedMSD]

Yes.
We will merge this PR into main if we leave the command to generate the config we use everywhere else?
We should mention the Bun's support, because a lot of users in our community use it

[MasedMSD]

I mean, this PR has been hanging around for a long time and we need to do something about it. Either put it on hold or get on with it

[KnorpelSenf]

I don't care if you use the command or not and I'm not opposed to mentioning bun support

[MasedMSD]

I'm not opposed to mentioning bun support

Great, I'll take care of that PR

[KnorpelSenf]

I mean, this PR has been hanging around for a long time and we need to do something about it. Either put it on hold or get on with it

That's true, what was stopping you?

[KnorpelSenf]

I'm not opposed to mentioning bun support

Great, I'll take care of that PR

Nice

[KnorpelSenf]

Suggested change

	On Deno and Bun you can send `Blob` objects, too.
	On Deno and Bun, you can send `Blob` objects, too.