1. The users of this style guide will probably expect that all of the rules that it prescribes will be enforced by eslint. However, this is not the case - there is a secret, non-documented segmentation where some rules are enforced and others are not, because they would be "too noisy on a legacy codebase". An example of a problematic rule like this is covered in issue #2020. I propose that all of

[Given REPL](https://babeljs.io/en/repl#?browsers=&build=&builtIns=false&spec=false&loose=true&code_lz=MYGwhgzhAEBCkFNoG8BQ1rAPYDsIBcAnAV2Hy0OgAoA3MEAShXQ2nwAsBLCAOjpGgBeaPwDcLAL4sA5gnxsEBKkzStohOcUI42XXmMmopqUJBgB5AEYAraAgAe-BDgAmMeBCSrMuAiTIU1PwqLBgQxAAOCIS09AyGGAD0idDmNNGEnC5IsvhOlGCu0MSe0OFRhDJyCkohahr4Wjrl0TxOBOIYUsbYePJYNkLQOAgA7qk2VETECAzivRBYIAg8IFjSVAPWbYr4cya-Sytm0fibNjsEADTQAOQAkjRYANac

🐛 bug report

loadConfig should emit a codeframe on a parse error:

https://github.com/parcel-bundler/parcel/blob/2f6274311889cad76fbdf2dafe60fc23478476d6/packages/core/utils/src/config.js#L80

This is for example used for loading .postcssrc.

🤔 Expected Behavior

See screenshot in parcel-bundler/parcel#4420

😯 Current Behavior

With an invalid `.p

Describe the issue / bug.

I added these configs in launch.js,

After F5 debug, already vscode debugging child processes.

but, breakpoint in main process used in folder

Some of the current background image selections have low contrast against the text or could be better quality images that better relate to selected verticals. This may be irrelevant if we decide to remove the image altogether.

The documentation states that this is Glide's structure, but specifically mentions adding the track attribute. So if that's required, is the HTML class structure also required or is it just for example?

<div class="glide">
  <div class="glide__track" data-glide-el="track">
    <ul class="glide__slides">
      <li class="glide__slide">0</li>
      <li class="glide__slide">1</li>