Deno strives to be browser compatible where possible; that means we use quite a few Web APIs.

There is not much docs for supported Web APIs at the moment and before 1.0 is released that situation must change. Some of APIs and not fully aligned to spec, while others are not fully implemented (#3557). All that knowledge should be written down and presented to end users to avoid multiple question

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

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

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

Describe the bug
The open command uses the bat crate to nicely render text files.
The docs here: https://www.nushell.sh/book/configuration.html#nushell-configuration-with-config-toml
say that setting the [textview] vcs_modification_markers option to true causes it to show modification markers, but it doesn't currently work. However, running bat on the same file does show modific

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) ->

What problem does this solve or what need does it fill?

When doing more complex work with bundles, users often end up combining two related bundles, overwriting all values set when they add the second bundle.

What solution would you like?

Add try_insert_bundle(bundle: impl Bundle), try_insert::<C: Component>(component: Component) commands.

These act like their non-try version

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

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