Markdown

Marked version:
3.x.x

Describe the bug
A clear and concise description of what the bug is.

Right now, import {use} from "markedjs" does not work, this worked in 2.x.x.

To Reproduce
Steps to reproduce the behavior:

Install & import it.
The DefinitelyTyped definitions also mark this incorrectly as being supported still.

A workaround is importing one of the structur

Explain the problem.

Converting the following:

pandoc -f gfm -t asciidoctor <<EOF
- [ ] a
- [x] b
EOF

produces:

* ☐ a
* ☒ b

instead of using the checklist syntax (see asciidoctor docs):

* [ ] a
* [x] b

This seems related to [the recently fixed org-mode r

Bug Report

What happened?

Im working on a project management system using logseq, and are using custom.css styled tags for easier overview. And noticed that the queries returned does not render the tags with the same css style as the pages.

The tags are in this example stored in a property named "status"

<img width="1101" alt="Screenshot 2022-07-16 at 09 09 57" src="https://user-images.githubuse

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

When autocompleting link opened with [[:
Current behavior:
Foam shows proposition list, where you can find filenames of available documents with additional preview of the content. When position is picked, Foam fills [[]] link with shortest possible file identifier like [[file1]] for file1.md.

Expected behavior:

Currently, few icons are not visible in dark theme. Make them visible by using theme neutral icons. May be we can make use of https://shields.io/ to generate our own kind of badges. For eg: Javascript.

What steps are needed to reproduce the bug?

test.scss

$frames: ("one", "two", "three");

@each $name in $frames {
  @keyframes frame-#{$name} {
    /* CSS ... */
  }
}

$ npx stylelint test.scss

test.scss
 4:14  ✖  Expected keyframe name to be kebab-case  keyframes-name-pattern

The name is kebab case, but due to the string interpolation, the line is f