Now that Prettier 2.0 has been released with its improved CLI, I think we should add a section do the docs showing a recommended example setup.

1. Recommend using an editor extension that lets you run Prettier from your editor. Link to popular extensions. Maybe add some tips on how to configure for example prettier-vscode.
2. Recommend adding an empty ({}) .prettierrc.json to signify to edit

Clearly describe the bug

"false-positive" no-descending-specificity with "empty" definitions (see below)

Which rule, if any, is the bug related to?

no-descending-specificity

What code is needed to reproduce the bug?

    nav {
      display: inline-block;
      a {
        display: inline-block;
      }
    }

    a,
    button,
    label {
      &:focus,

I'm testing out madge on my TS RN codebase, and I'm surprised to see that it just magically works without specifying a tsconfig.

For example
yarn madge --circular --extensions ts,tsx ./

Although this is cool and exciting, it gives me pause because the documentation doesn't explain how this works. I read the source and followed the path through a series of external npm dependencies. Af

I'd like to use CSS modules by default for all my SCSS code, but disable it for Bootstrap SCSS files.

Right now I have this setup:

Encore.configureCssLoader(options => {
    options.modules = true;
    options.camelCase = true;
})

It works fine, but if I import Bootstrap SCSS files in my project:

require('bootstrap/scss/bootstrap.scss');

It gets compiled t

Type of Issue

[ ] Bug Report
[x] Feature Request

Description

Currently, contributing to this project can be hard especially for beginners like me who do not understand the project structure.

How To Reproduce

Put yourself into a beginner's shoes.

Let's say you want to contribute code to resolve a feature request (something like #1180, which introduces support

In twig, whenever a comment starts the first non-empty line following an opening tag, the attributes are forced onto a new line and indented.

<div class="container text-white-90">

  {# brand/ logo #}

becomes

<div 
  class="container text-white-90">

  {# brand/ logo #}

I'm using the Twig Language VS Code extension, but this also happens on the website

Describe the bug
In your documentation, it clearly states:

You may add as many html pages as you’d like to the root level directory, they will automatically be copied and minified into the dist/ folder upon building your site.

So I don't know if this a bug report or a feature request:

I want users to be able to visit website.com/survey instead of survey.html so I've put a

A div element is a semantically neutral element that doesn't not convey its meaning or state to the accessibility layer. These examples should use the ARIA progressbar role (or use native HTML semantics) and update the state using the various state attributes (using JS). See https://www.w3.org/TR/wai-aria/roles#progressbar for details.

老哥你好，好像有个bug

Markdown的 [toc]语法是根据后面的Markdown节点自动生成一个目录，比如

[TOC]
#header1

会在header1的前面生成一个header1超链接，指向#header1，点击之后自动跳到header1锚点。而header1标题的位置就是一个超链接，比如<a href="#header1">xxx</a>

但是你这里的实现好像是把目录的锚点用一串数值代替了，header1处的超链接变成了<a href="#1234567890">xxx</a>。因此，如果点击[toc]自动生成的目录的话，无法跳到对应的锚点。

https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-describedby_attribute

The aria-describedby attribute is used to indicate the IDs of the elements that describe the object. It is used to establish a relationship between widgets or groups and text that described them. This is very similar to aria-labelledby: a label describes the essence of an object,

The CSS for Description list title field needs to be changed for better contrast. It is barely visible with the dark theme.

Thank you.