I am looking into variants and i feel like its a bit confusing which is the old api and which is the new one?

I feel like I should just be able to drop the variant function onto a component and give it scale="accents" and then if I pass variant="info" then it should look in the theme object for accents and pull the info key inside that yet it doesn't do that unless I write `variants: {

Now it's possible to namespace a theme by using a themeNamespace property for the component. This avoids collisions between modules of different components using the same classname. It's a feature that it's working and it's published but not documented. We need to write a section detailing the API which is very simple!

Links don't work with a base path like on gh-pages, as seen here https://jxnblk.com/mdx-docs

• Add docs for how to handle publishing to gh-pages

I am using 'code' package on arch linux and this app doesn't seem to query the themes. Whenever I click the switcher, it gets disabled. I am guessing this may be the problem:

vscode_extensions_paths = ['/snap/vscode/current/usr/share/code/resources/app/extensions',
                                   '/usr/share/code/resources/app/extensions',
str(Path.home().joinpath('.vscode', 'ex

Not 100 % sure but I don't think the documentation mentions anything about reserved words in pattern definitions?

  /**
   * Reserved words.
   *
   * @var array
   */
  protected $reserved = [
    'id',
    'type',
    'theme',
    'context',
    'use',
    'attributes',
  ];

It would be good to document them as the resulting error message is a bit cryptic.

here is my HTML code:

<link rel="icon" media="screen" href="A" type="image/png" />
<link rel="icon" media="(prefers-color-scheme:dark)" href="B" type="image/png" />
<link rel="icon" media="(prefers-color-scheme:light)" href="C" type="image/png" />

The first link is used as a fallback for those browser doesn't support prefers-color-scheme.

(Tested with Chrome)
When URL A point