Bug report

Summary

Enable the heading-increment rule to our remark-lint config.

Followup of #21919

Motivation

Headings should only increase 1 level at a time for accessibility.

Steps

1. Delete the [line in `.rema

Was checking babel/babel#11478 and testing out syntax and noticed we don't error with the normal "use this plugin/preset" like we do for proposals with JSX itself. @nicolo-ribaudo mentioned it's probably since jsx is implemented as a normal plugin so we didn't have `this.expectPlugin("recordAndT

🐛 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 bug
The content of the the svelte file is a large HTML chunk, withouy any script logics or styling being involved. Max stack size exceeded error while compiling.

To Reproduce
https://svelte.dev/repl/a9dfcc17551c4aeb95e8fe748a97061d?version=3.20.1

Expected behavior
Compiling should not break

Information about your Svelte project:
Svelte 3.20.1, Rollup, Wind

Please see previous #1522 for backstory.

December 1st, 2017 the core team came together to take on Marked. Since then a lot has happened...a lot. Some changes in direction we wanted to talk about:

1. Spec-compliance, semver, and a 1.0 release
2. Make Marked more extensible ra

Hello, could we somehow document #522 / provide a better error message? I've spent waaaaay too much time trying to solve the issue before finding the already existing solution:/

Even better - fix it, instead of a work-around?

Thanks!

Is your feature request related to a problem? Please describe.
No.

Describe the solution you'd like
I'd like the source code to be automatically clang-formatted according to my settings anytime the code is compiled. That is, don't require me to use the contextual menu or keyboard shortcut to format the code. Just auto-format it; just like the code is auto-compiled too.

Well, ther

Problem

walt-cli package when linking multiple .walt files together can "wrap" the modules in a stand-alone JS module. The resulting module is too large because it serialized the dependency tree with the AST information encoded directly into the output, resulting in a massive amount of js.

Encoding the dependencies into the file is done to ensure the module can be used stand-alone in br

https://github.com/phenomic/phenomic/blob/master/packages/preset-react-app/docs/getting-started/5.md

When we tell people to add this section to their component after the list, it creates two nodes that are not contained. It is a ul and a div.

We should somehow mention that you need to surround the two in a div before adding that extra snippet to Older Posts, because react will only l

This program doesn't report an error:

type O = { x :: Number, x :: Number }

but it should. The related value has a well-formedness error:

{x : 10, x: 20}

@TimHambourger made a very useful test harness, we could integrate it in our CI somehow (if @TimHambourger is ok with that).

Note we can keep a seperated repo.

Hey! I just fixed up some spelling, etc in the readme, but I don't have permissions to create a remote branch so I can create a PR from it. Is this allowed?

We should tidy up some bits of our code:

Path Joins

• path.join should not contain multiple path components in an argument.

We should replace these joins:

path.join(dir.name, "build/node", "package.json")

with:

path.join(dir.name, "build", "node", "package.json")

_Originally posted by @pouya-eghbali in clio-lang/clio#129 (comment)