forbid via eslint to use the Buffer class in the code

[Danil42Russia]

In a comment #1565 (comment) @verytactical wrote:

Buffer is Node's non-standard API for binary data, while there is platform-agnostic Blob. When we build browser version of @tact-lang/compiler, we have to include a polyfill for Buffer.

While there are other places that use Buffer, we're working hard to remove them. I'd consider removing Buffer support here too.

So my suggestion is to disallow it via an eslint rule. This is a concept, if you like it I will add ignore existing errors.

Checklist

• I have updated CHANGELOG.md
• I have run all the tests locally and no test failure was reported
• I have run the linter, formatter and spellchecker
• I did not do unrelated and/or undiscussed refactorings

[anton-trunov]

So my suggestion is to disallow it via an eslint rule. This is a concept, if you like it I will add ignore existing errors.

I'm in favor of disallowing Buffer, but we should not just ignore all the existing errors, it needs to be case-by-case.

Also, this issue is relevant here: #1434.

[Danil42Russia]

So my suggestion is to disallow it via an eslint rule. This is a concept, if you like it I will add ignore existing errors.

I'm in favor of disallowing Buffer, but we should not just ignore all the existing errors, it needs to be case-by-case.

Also, this issue is relevant here: #1434.

Yes, you're right, but this will prohibit adding new code using Buffer.
I'm going to create an issue to replace it, and I'll specify it in the 'eslint' error. Well, I must say what to use instead of it.