feat: support deno and modern chromium

[idranme]

No description provided.

[idranme]

PTAL @sindresorhus

[sindresorhus]

Deno supports Node.js packages. We are not going to add lots of custom code for Deno.

[sindresorhus]

As for the Firefox support, can you link to a source that documents the support for ANSI escapes?

[idranme]

Deno supports Node.js packages. We are not going to add lots of custom code for Deno.

But the polyfill it introduces automatically can cause unnecessary privileges to be requested. And it also reduces the speed of starting work.

[idranme]

As for the Firefox support, can you link to a source that documents the support for ANSI escapes?

It really doesn't support ANSI, which I was wrong about. I will fix it.

[sindresorhus]

But the polyfill it introduces automatically can cause unnecessary privileges to be requested.

You should open an issue on Deno about that. This sounds like a bug in the polyfill.

[idranme]

But the polyfill it introduces automatically can cause unnecessary privileges to be requested.

You should open an issue on Deno about that. This sounds like a bug in the polyfill.

I'm not sure if this is a bug, but I can sure that introducing polyfill slows down startup.

[idranme]

But the polyfill it introduces automatically can cause unnecessary privileges to be requested.

You should open an issue on Deno about that. This sounds like a bug in the polyfill.

denoland/deno#16848 (comment)
This is not a bug in polyfill.

[Qix-]

Not a huge fan of this. For years javascript standards have diverged creating hell on earth for package maintainers. This seems to be multiplicative maintenance overhead...

[idranme]

Not a huge fan of this. For years javascript standards have diverged creating hell on earth for package maintainers. This seems to be multiplicative maintenance overhead...

I will open a PR later to rework it. I believe we can solve this problem.

[idranme]

Not a huge fan of this. For years javascript standards have diverged creating hell on earth for package maintainers. This seems to be multiplicative maintenance overhead...

See #142