In version typescript 4.1 the option "noUncheckedIndexedAccess" has been added.
I would strongly advise deno to support the ability to set this option.

https://www.typescriptlang.org/tsconfig#noUncheckedIndexedAccess

It would be great to make use of the new syntect API to detect when a syntax definition has some context references (specifically push/set targets - missing includes are not such a problem and can be just treated as warnings) which couldn't be linked/resolved and fail the CI build. sharkdp/bat#915 (comment)

It's always a good idea to work on documentation. I think it would also be good to restructure the README:

• Add a quick link section at the top of the readme (see https://github.com/sharkdp/bat)
• Extend the tutorial (rename "How to use"?)
• Move the "Parallel command execution" section inside the "How to use" section). See also: #605
• Move "Installation" section below the

The documentation contains a few references to issues from the now archived yewstack/docs repository.
Since the docs repository is read-only, the same issues should be re-created here and the links in the docs should be updated to point to the new issue.

"Contribute to our docs" links

• Page: [Components Lifecycle Diagram](https://yew.rs/docs/conce

Is your feature request related to a problem? Please describe.
Many of our packages seem to have a little bloat. We want to reduce our environmental impact (and also the time spent downloading / building / shipping).

Describe the solution you'd like
Every npm package should have an .npmignore that prunes non-necessary stuff
Remove tests / examples from crates

-ALWAYS ship the li

Is your feature request related to a problem? Please describe.
We're currently using both which and ichwh. The ichwh crate is meant for use in async/await use cases, though because we have rewritten to use sync iterators, we no longer need this functionality.

Describe the solution you'd like
Let's rewrite the ichwh usage to use a simpler, sync approach. This would let us remov

Right now any StyleSheet has a list of functions without a default implementation. Implementing a StyleSheet is really annoying, because you have to override all of the functions and not just the thing you want to change.

I recently wanted to just change the border_radius of a text_input and I had to write the following code.

impl StyleSheet for Styles {
    fn active(&self) ->

How can Bevy's documentation be improved?

When we search for common items in Bevy's docs, we often see two or three duplicate entries due to re-exporting.

This can be disabled using #[doc(hidden)] above the re-exports. See: https://doc.rust-lang.org/beta/rust-by-example/meta/doc.html#hidden.

IMO the re-exports should be hidden, as the root path is the most informative about what th

Currently, with dark theme only available colour scheme is grey shades, while light mode offers multiple colour schemes. With only greys, it can be hard to tell difference between shades.

It might be good idea to add (more) colour schemes to dark mode. Even just copying schemes from light mode would be a good start, although they might need a bit of tweaking to avoid heavy contrast with backgro

Subject of the issue

When attempting to do a login to an account that has 2FA enabled, but without the 2FA details, it seems to return the wrong error response. Not just the message, but the whole object is different. I understand that this is likely not a priority considering everything works, but for parity's sake, it would be nice to have this implemented the right way.

I also noticed t