@mirrordown/remd-spoiler 0.1.1 → 0.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +86 -0
- package/README.md +19 -6
- package/dist/index.d.mts.map +1 -1
- package/dist/index.mjs +10 -4
- package/dist/index.mjs.map +1 -1
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -1,6 +1,92 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
3
|
|
|
4
|
+
|
|
5
|
+
## 0.1.2
|
|
6
|
+
<sub>2026-11-17</sub>
|
|
7
|
+
|
|
8
|
+
- *(patch)*
|
|
9
|
+
Fixes for cases where a `||spoiler||` formed in one engine and not another, which either hides text you meant to show or shows text you meant to hide.
|
|
10
|
+
|
|
11
|
+
- **Without `spoilerHastHandlers`, the remark plugin keeps the content covered** (remark). The handlers are still required for a spoiler that can be revealed; this is what happens when they are not passed to `remark-rehype`.
|
|
12
|
+
|
|
13
|
+
```markdown
|
|
14
|
+
a ||b|| c
|
|
15
|
+
```
|
|
16
|
+
|
|
17
|
+
Was `a <div>b</div> c`, the content in the clear. Now `a <span class="markdown-spoiler-content">b</span> c`, which the stylesheet covers and nothing reveals.
|
|
18
|
+
|
|
19
|
+
- **A spoiler in a table cell forms** (remark, Sätteri). In a cell the pipes have to be written `\|`.
|
|
20
|
+
|
|
21
|
+
```markdown
|
|
22
|
+
| h |
|
|
23
|
+
| - |
|
|
24
|
+
| \|\|x\|\| |
|
|
25
|
+
```
|
|
26
|
+
|
|
27
|
+
Was the text `||x||` in the cell. Now a spoiler, as in markdown-it.
|
|
28
|
+
|
|
29
|
+
- **An attribute block written right after a spoiler is read and dropped** (Sätteri, with its `attributes` feature on).
|
|
30
|
+
|
|
31
|
+
```markdown
|
|
32
|
+
||secret||{.danger}
|
|
33
|
+
```
|
|
34
|
+
|
|
35
|
+
Was `<p class="danger">` around the spoiler, and mid-paragraph the block stayed on the page as text. Now the paragraph has no class and the block is gone, as in markdown-it and remark.
|
|
36
|
+
|
|
37
|
+
- **Escaped pipes stay text after another plugin's span** (remark, Sätteri).
|
|
38
|
+
|
|
39
|
+
```markdown
|
|
40
|
+
==a== \||b||
|
|
41
|
+
```
|
|
42
|
+
|
|
43
|
+
Was a spoiler around `b`. Now `<mark>a</mark> ||b||`, as in markdown-it.
|
|
44
|
+
|
|
45
|
+
- **An escape is still honoured after smart punctuation** (Sätteri, with smart punctuation on).
|
|
46
|
+
|
|
47
|
+
```markdown
|
|
48
|
+
"q" \||a||
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
Was a spoiler around `a`. Now `“q” ||a||`.
|
|
52
|
+
|
|
53
|
+
- **A pipe written as a character reference is not a delimiter** (remark, Sätteri).
|
|
54
|
+
|
|
55
|
+
```markdown
|
|
56
|
+
||text||
|
|
57
|
+
```
|
|
58
|
+
|
|
59
|
+
Was a spoiler around `text`. Now the text `||text||`.
|
|
60
|
+
|
|
61
|
+
- **The text of an autolink is left alone** (remark, Sätteri).
|
|
62
|
+
|
|
63
|
+
```markdown
|
|
64
|
+
<http://x/||b||>
|
|
65
|
+
```
|
|
66
|
+
|
|
67
|
+
Was a link with a spoiler around `b` in its text. Now the link text is the URL as written.
|
|
68
|
+
|
|
69
|
+
- **An escaped character or a character reference beside the pipes counts as punctuation** (remark, Sätteri). This decides whether a pair of pipes can open or close.
|
|
70
|
+
|
|
71
|
+
```markdown
|
|
72
|
+
a||\*b||
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
Was `a` and a spoiler around `*b`. Now the text `a||*b||`, as in markdown-it.
|
|
76
|
+
|
|
77
|
+
- **A backslash line break right after the opening pipes does not stop them from opening** (remark, Sätteri).
|
|
78
|
+
|
|
79
|
+
```markdown
|
|
80
|
+
(||\
|
|
81
|
+
a||
|
|
82
|
+
```
|
|
83
|
+
|
|
84
|
+
Now a spoiler around the line break and `a`, as in markdown-it.
|
|
85
|
+
|
|
86
|
+
- **Spoilers nest up to 50 deep** (all engines). The pipes of deeper ones stay text. Sätteri used to reject the whole document when spoilers nested too deep: each one counts twice toward its limit of 128 levels.
|
|
87
|
+
|
|
88
|
+
The guide now lists the differences between engines that remain.
|
|
89
|
+
|
|
4
90
|
## 0.1.1
|
|
5
91
|
<sub>2026-10-28</sub>
|
|
6
92
|
|
package/README.md
CHANGED
|
@@ -17,7 +17,7 @@ The entire interaction is built from HTML and CSS only — a `<label>` wrapping
|
|
|
17
17
|
</label>
|
|
18
18
|
```
|
|
19
19
|
|
|
20
|
-
The checkbox is the only interactive control, so it stays keyboard-operable and is announced by screen readers as a spoiler control
|
|
20
|
+
The checkbox is the only interactive control, so it stays keyboard-operable and is announced by screen readers as a spoiler control. The stylesheet hides text by making it transparent on the bar, and hides elements inside the spoiler (emphasis, links, code) with `visibility: hidden`: plain text stays in the page, so it is hidden from sight and not necessarily from a screen reader.
|
|
21
21
|
|
|
22
22
|
## Syntax
|
|
23
23
|
|
|
@@ -29,9 +29,21 @@ The killer was ||the butler|| all along, hidden in ||the conservatory||.
|
|
|
29
29
|
|
|
30
30
|
In renderers without the plugin, `||…||` renders as plain text.
|
|
31
31
|
|
|
32
|
+
A backslash keeps a delimiter literal (`\||not hidden||`), and so does writing a pipe as a character reference (`|`). A table cell is the exception: a pipe there has to be written `\|`, so a spoiler in a cell is written `\|\|hidden\|\|`.
|
|
33
|
+
|
|
34
|
+
Spans have to nest. When a spoiler crosses another span or crosses emphasis (`||a *b|| c*`), each engine resolves it its own way, and in remark and Sätteri the result depends on the order the plugins are listed in. Spoilers nest up to 50 deep; the pipes of deeper ones stay text.
|
|
35
|
+
|
|
36
|
+
A spoiler takes no attributes: with the [`attrs`](/guide/plugins/attrs) plugin or Sätteri's `attributes` feature on, an attribute block written right after one (`||text||{.name}`) is read and dropped in every engine.
|
|
37
|
+
|
|
38
|
+
A few things differ between the engines:
|
|
39
|
+
|
|
40
|
+
- In image alt text (``), markdown-it drops the pipes and remark and Sätteri keep the text as written.
|
|
41
|
+
- The remark plugin reads escapes from the source, so it needs the file: `processor.runSync(tree)` on a tree alone treats `\||` as `||`.
|
|
42
|
+
- In a table cell, two backslashes before a pipe (`\\|`) are a backslash and an escaped pipe to markdown-it, and an escaped backslash and a cell separator to remark and Sätteri, so a row holding them splits into cells differently before any plugin runs.
|
|
43
|
+
|
|
32
44
|
### Rich inline content
|
|
33
45
|
|
|
34
|
-
A spoiler can wrap any inline markup — emphasis, code, links — and it stays obscured until revealed. A long spoiler wraps across lines with each line getting its own bar, just like Discord.
|
|
46
|
+
A spoiler can wrap any inline markup — emphasis, code, links — and it stays obscured until revealed. One exception today: with the [`ruby`](/guide/plugins/ruby) plugin on, braces around text that holds a spoiler are read as a ruby, whose first `|` is its separator, so `{note: ||secret||}` renders `note:` with `|secret||` printed above it. A long spoiler wraps across lines with each line getting its own bar, just like Discord.
|
|
35
47
|
|
|
36
48
|
````markdown
|
|
37
49
|
The recipe needs ||**two** cups of `flour` and a
|
|
@@ -48,7 +60,7 @@ Careful, dinner photo incoming: || plugin (`||!![…]()||`) for a spoilered image that is also click-to-zoom once revealed.
|
|
63
|
+
Combine with the [`lightbox`](/guide/plugins/lightbox) plugin (`||!![…]()||`) for a spoilered image that is also click-to-zoom once revealed. The zoom button sits inside the spoiler and can take keyboard focus of its own, so today <kbd>Tab</kbd> then <kbd>Enter</kbd> opens the image without revealing it first.
|
|
52
64
|
|
|
53
65
|
````markdown
|
|
54
66
|
The reveal: ||!||
|
|
@@ -56,7 +68,7 @@ The reveal: ||!||
|
|
|
56
68
|
|
|
57
69
|
### Inside links
|
|
58
70
|
|
|
59
|
-
A spoiler works inside a link — the whole revealed content remains the link target.
|
|
71
|
+
A spoiler works inside a link — the whole revealed content remains the link target. The markup puts the spoiler's `<label>` and checkbox inside the `<a>`.
|
|
60
72
|
|
|
61
73
|
````markdown
|
|
62
74
|
Read [the ||shocking twist||](https://example.com) at your own risk.
|
|
@@ -64,7 +76,7 @@ Read [the ||shocking twist||](https://example.com) at your own risk.
|
|
|
64
76
|
|
|
65
77
|
## Accessibility
|
|
66
78
|
|
|
67
|
-
The spoiler is a real checkbox with `aria-label="spoiler"`, so assistive technology announces it as a control the user can operate
|
|
79
|
+
The spoiler is a real checkbox with `aria-label="spoiler"`, so assistive technology announces it as a control the user can operate. Keyboard users <kbd>Tab</kbd> to the spoiler and press <kbd>Space</kbd> to reveal it; a focus ring marks the current spoiler. Revealing is reversible (unlike Discord, which locks open) — a superset of the expected behavior.
|
|
68
80
|
|
|
69
81
|
## Customization
|
|
70
82
|
|
|
@@ -73,6 +85,7 @@ The stylesheet keeps its rules in `@layer markdown-spoiler`, so any unlayered CS
|
|
|
73
85
|
| Property | Default | Description |
|
|
74
86
|
| ----------------------------------- | ------------------------------------------- | --------------------------------------- |
|
|
75
87
|
| `--markdown-spoiler-bar` | `#202225` | Obscured bar color (text spoilers). |
|
|
88
|
+
| `--markdown-spoiler-bar-hover` | `--markdown-spoiler-bar` mixed 15% white | Bar color under the pointer. |
|
|
76
89
|
| `--markdown-spoiler-radius` | `0.25rem` | Bar corner radius. |
|
|
77
90
|
| `--markdown-spoiler-duration` | `0.15s` | Reveal transition duration. |
|
|
78
91
|
| `--markdown-spoiler-revealed` | `color-mix(in srgb, currentColor 8%, …)` | Background behind revealed text. |
|
|
@@ -93,7 +106,7 @@ Text spoilers work everywhere (checkbox + sibling selector). Image spoilers use
|
|
|
93
106
|
|
|
94
107
|
## Install
|
|
95
108
|
|
|
96
|
-
Install `@mirrordown/remd-spoiler`. You must also pass `spoilerHastHandlers` to `remarkRehype` and import the stylesheet:
|
|
109
|
+
Install `@mirrordown/remd-spoiler`. You must also pass `spoilerHastHandlers` to `remarkRehype` (without them a spoiler renders as a bar that cannot be revealed) and import the stylesheet:
|
|
97
110
|
|
|
98
111
|
```sh
|
|
99
112
|
npm install @mirrordown/remd-spoiler
|
package/dist/index.d.mts.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"index.d.mts","names":[],"sources":["../src/plugin.ts","../src/augment.ts"],"mappings":";;;;
|
|
1
|
+
{"version":3,"file":"index.d.mts","names":[],"sources":["../src/plugin.ts","../src/augment.ts"],"mappings":";;;;iBAUiB,oBAAoB;;;;;iBAMpB,gBAAgB;EAC/B;EACA,UAAU;EACV,OAAO;;UAOC;EACR,MAAM,MAAM,YAAY;EACxB,QAAQ,MAAM,SAAS,IAAI;;KAExB,kBAAkB,OAAO,WAAW,MAAM,YAAY;;qBAoC9C,qBAAqB,eAAe;;;;qBAOpC,eAAe,WAAW;;YCnE3B;IACR,SAAS;;YAGD;IACR,SAAS"}
|
package/dist/index.mjs
CHANGED
|
@@ -1,6 +1,7 @@
|
|
|
1
1
|
import { visit } from "unist-util-visit";
|
|
2
2
|
import { createDelimitedTransform, maskTreeEscapes } from "@mirrordown/core";
|
|
3
3
|
// src/plugin.ts
|
|
4
|
+
const MAX_DEPTH = 50;
|
|
4
5
|
/**
|
|
5
6
|
* Build the `<label><input><span>...</span></label>` hast subtree. The checkbox
|
|
6
7
|
* precedes the content span so CSS's `:checked ~ .content` combinator can reach
|
|
@@ -43,17 +44,22 @@ const remarkSpoiler = () => {
|
|
|
43
44
|
}),
|
|
44
45
|
wrap: (children) => ({
|
|
45
46
|
type: `spoiler`,
|
|
46
|
-
children
|
|
47
|
+
children,
|
|
48
|
+
data: {
|
|
49
|
+
hName: `span`,
|
|
50
|
+
hProperties: { className: [`markdown-spoiler-content`] }
|
|
51
|
+
}
|
|
47
52
|
})
|
|
48
|
-
});
|
|
53
|
+
}, MAX_DEPTH);
|
|
49
54
|
const transformer = (tree, file) => {
|
|
50
|
-
const
|
|
55
|
+
const source = String(file);
|
|
56
|
+
const restoreEscapes = maskTreeEscapes(tree, source);
|
|
51
57
|
const seen = /* @__PURE__ */ new WeakSet();
|
|
52
58
|
visit(tree, `text`, (_node, _index, parent) => {
|
|
53
59
|
if (!parent || seen.has(parent) || transform.built(parent)) return;
|
|
54
60
|
seen.add(parent);
|
|
55
61
|
const children = parent.children;
|
|
56
|
-
const next = transform(children, parent.type);
|
|
62
|
+
const next = transform(children, parent.type, source);
|
|
57
63
|
if (next !== children) parent.children = [...next];
|
|
58
64
|
return 0;
|
|
59
65
|
});
|
package/dist/index.mjs.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"index.mjs","names":[],"sources":["../src/plugin.ts"],"sourcesContent":["import { visit } from \"unist-util-visit\";\nimport type { Plugin, Transformer } from \"unified\";\nimport type { Data, Parent, PhrasingContent, Root } from \"mdast\";\nimport type { Element, ElementContent, Properties } from \"hast\";\nimport { createDelimitedTransform, maskTreeEscapes } from \"@mirrordown/core\";\n\n/** Optional data carried by a {@link Spoiler} node. */\nexport interface SpoilerData extends Data {}\n\n/**\n * An mdast node for `||spoiler||` text, rendered as a click-to-reveal spoiler\n * (a `<label>` wrapping a checkbox and a content `<span>`).\n */\nexport interface Spoiler extends Parent {\n type: `spoiler`;\n children: PhrasingContent[];\n data?: SpoilerData | undefined;\n}\n\n// Minimal hast-handler surface. remark-rehype's real `State`/`Handler` types\n// carry the whole conversion API; we only need `all()` to convert this node's\n// mdast children into hast. Typed locally to avoid a dependency on\n// mdast-util-to-hast just for two type names.\ninterface HastState {\n all: (node: Spoiler) => ElementContent[];\n patch: (from: Spoiler, to: Element) => void;\n}\ntype SpoilerHandler = (state: HastState, node: Spoiler) => Element;\n\n/**\n * Build the `<label><input><span>...</span></label>` hast subtree. The checkbox\n * precedes the content span so CSS's `:checked ~ .content` combinator can reach\n * it; the content is a following sibling, not a child, of the checkbox.\n */\nconst buildSpoilerHast = (state: HastState, node: Spoiler): Element => {\n const inputProps: Properties = {\n type: `checkbox`,\n class: `markdown-spoiler-toggle`,\n \"aria-label\": `spoiler`\n };\n const input: Element = {\n type: `element`,\n tagName: `input`,\n properties: inputProps,\n children: []\n };\n const content: Element = {\n type: `element`,\n tagName: `span`,\n properties: { class: `markdown-spoiler-content` },\n children: state.all(node)\n };\n const result: Element = {\n type: `element`,\n tagName: `label`,\n properties: { class: `markdown-spoiler` },\n children: [input, content]\n };\n state.patch(node, result);\n return result;\n};\n\n/** mdast-to-hast handler for spoiler nodes, for use with `remark-rehype`. */\nexport const spoilerHastHandlers: Record<string, SpoilerHandler> = {\n spoiler: buildSpoilerHast\n};\n\n/**\n * remark plugin for Discord-style spoiler syntax (`||text||`), wrapping each match in a {@link Spoiler} node. Pair with {@link spoilerHastHandlers} via `remarkRehype({ handlers: spoilerHastHandlers })` so the node renders as a click-to-reveal spoiler. The scan is shared with markdown-it's pairing rules and the Sätteri plugin through `@mirrordown/core`, and the output is byte-identical to `@mirrordown/mdit-spoiler`.\n */\nexport const remarkSpoiler: Plugin<[], Root> = () => {\n const transform = createDelimitedTransform<PhrasingContent>(
|
|
1
|
+
{"version":3,"file":"index.mjs","names":[],"sources":["../src/plugin.ts"],"sourcesContent":["import { visit } from \"unist-util-visit\";\nimport type { Plugin, Transformer } from \"unified\";\nimport type { Data, Parent, PhrasingContent, Root } from \"mdast\";\nimport type { Element, ElementContent, Properties } from \"hast\";\nimport { createDelimitedTransform, maskTreeEscapes } from \"@mirrordown/core\";\n\n// A spoiler nested deeper than this stays text, as in the markdown-it and Sätteri plugins: Sätteri rejects a document whose content nests deeper than 128 levels, and a spoiler is two levels there (the label and the content span).\nconst MAX_DEPTH = 50;\n\n/** Optional data carried by a {@link Spoiler} node. */\nexport interface SpoilerData extends Data {}\n\n/**\n * An mdast node for `||spoiler||` text, rendered as a click-to-reveal spoiler\n * (a `<label>` wrapping a checkbox and a content `<span>`).\n */\nexport interface Spoiler extends Parent {\n type: `spoiler`;\n children: PhrasingContent[];\n data?: SpoilerData | undefined;\n}\n\n// Minimal hast-handler surface. remark-rehype's real `State`/`Handler` types\n// carry the whole conversion API; we only need `all()` to convert this node's\n// mdast children into hast. Typed locally to avoid a dependency on\n// mdast-util-to-hast just for two type names.\ninterface HastState {\n all: (node: Spoiler) => ElementContent[];\n patch: (from: Spoiler, to: Element) => void;\n}\ntype SpoilerHandler = (state: HastState, node: Spoiler) => Element;\n\n/**\n * Build the `<label><input><span>...</span></label>` hast subtree. The checkbox\n * precedes the content span so CSS's `:checked ~ .content` combinator can reach\n * it; the content is a following sibling, not a child, of the checkbox.\n */\nconst buildSpoilerHast = (state: HastState, node: Spoiler): Element => {\n const inputProps: Properties = {\n type: `checkbox`,\n class: `markdown-spoiler-toggle`,\n \"aria-label\": `spoiler`\n };\n const input: Element = {\n type: `element`,\n tagName: `input`,\n properties: inputProps,\n children: []\n };\n const content: Element = {\n type: `element`,\n tagName: `span`,\n properties: { class: `markdown-spoiler-content` },\n children: state.all(node)\n };\n const result: Element = {\n type: `element`,\n tagName: `label`,\n properties: { class: `markdown-spoiler` },\n children: [input, content]\n };\n state.patch(node, result);\n return result;\n};\n\n/** mdast-to-hast handler for spoiler nodes, for use with `remark-rehype`. */\nexport const spoilerHastHandlers: Record<string, SpoilerHandler> = {\n spoiler: buildSpoilerHast\n};\n\n/**\n * remark plugin for Discord-style spoiler syntax (`||text||`), wrapping each match in a {@link Spoiler} node. Pair with {@link spoilerHastHandlers} via `remarkRehype({ handlers: spoilerHastHandlers })` so the node renders as a click-to-reveal spoiler. The scan is shared with markdown-it's pairing rules and the Sätteri plugin through `@mirrordown/core`, and the output is byte-identical to `@mirrordown/mdit-spoiler`.\n */\nexport const remarkSpoiler: Plugin<[], Root> = () => {\n const transform = createDelimitedTransform<PhrasingContent>(\n `|`,\n {\n text: (value) => ({ type: `text`, value }),\n // `spoilerHastHandlers` builds the element and never reads this data. It is what renders when the handlers were not passed to `remark-rehype`: the content span alone, which the stylesheet covers and nothing can reveal, where the default for an unknown node is a `<div>` with the content in the clear.\n wrap: (children): Spoiler => ({\n type: `spoiler`,\n children,\n data: {\n hName: `span`,\n hProperties: { className: [`markdown-spoiler-content`] }\n }\n })\n },\n MAX_DEPTH\n );\n\n const transformer: Transformer<Root> = (tree, file) => {\n // Escapes are resolved before this runs; mask escaped characters so a backslash-escaped delimiter is not matched, as in markdown-it.\n const source = String(file);\n const restoreEscapes = maskTreeEscapes(tree, source);\n const seen = new WeakSet<Parent>();\n visit(tree, `text`, (_node, _index, parent: Parent | undefined) => {\n // Spoilers the scan built have already had their content scanned.\n if (!parent || seen.has(parent) || transform.built(parent)) return;\n seen.add(parent);\n // A text node's parent holds phrasing content.\n // oxlint-disable-next-line typescript/no-unsafe-type-assertion\n const children = parent.children as PhrasingContent[];\n const next = transform(children, parent.type, source);\n if (next !== children) parent.children = [...next];\n // Walk the restructured children from the start; this parent is done.\n return 0;\n });\n restoreEscapes();\n };\n\n return transformer;\n};\n"],"mappings":";;;AAOA,MAAM,YAAY;;;;;;AA8BlB,MAAM,oBAAoB,OAAkB,SAA2B;CAkBrE,MAAM,SAAkB;EACtB,MAAM;EACN,SAAS;EACT,YAAY,EAAE,OAAO,mBAAmB;EACxC,UAAU,CAAC;GAfX,MAAM;GACN,SAAS;GACT,YAAY;IAPZ,MAAM;IACN,OAAO;IACP,cAAc;GAKO;GACrB,UAAU,CAAC;EAYI,GAAG;GATlB,MAAM;GACN,SAAS;GACT,YAAY,EAAE,OAAO,2BAA2B;GAChD,UAAU,MAAM,IAAI,IAAI;EAMA,CAAC;CAC3B;CACA,MAAM,MAAM,MAAM,MAAM;CACxB,OAAO;AACT;;AAGA,MAAa,sBAAsD,EACjE,SAAS,iBACX;;;;AAKA,MAAa,sBAAwC;CACnD,MAAM,YAAY,yBAChB,KACA;EACE,OAAO,WAAW;GAAE,MAAM;GAAQ;EAAM;EAExC,OAAO,cAAuB;GAC5B,MAAM;GACN;GACA,MAAM;IACJ,OAAO;IACP,aAAa,EAAE,WAAW,CAAC,0BAA0B,EAAE;GACzD;EACF;CACF,GACA,SACF;CAEA,MAAM,eAAkC,MAAM,SAAS;EAErD,MAAM,SAAS,OAAO,IAAI;EAC1B,MAAM,iBAAiB,gBAAgB,MAAM,MAAM;EACnD,MAAM,uBAAO,IAAI,QAAgB;EACjC,MAAM,MAAM,SAAS,OAAO,QAAQ,WAA+B;GAEjE,IAAI,CAAC,UAAU,KAAK,IAAI,MAAM,KAAK,UAAU,MAAM,MAAM,GAAG;GAC5D,KAAK,IAAI,MAAM;GAGf,MAAM,WAAW,OAAO;GACxB,MAAM,OAAO,UAAU,UAAU,OAAO,MAAM,MAAM;GACpD,IAAI,SAAS,UAAU,OAAO,WAAW,CAAC,GAAG,IAAI;GAEjD,OAAO;EACT,CAAC;EACD,eAAe;CACjB;CAEA,OAAO;AACT"}
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@mirrordown/remd-spoiler",
|
|
3
3
|
"description": "A remark plugin for Discord-style spoiler syntax (||text||), rendering click-to-reveal spoilers.",
|
|
4
|
-
"version": "0.1.
|
|
4
|
+
"version": "0.1.2",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"author": "Drake Costa <drake@saeris.io> (https://saeris.gg)",
|
|
7
7
|
"repository": {
|
|
@@ -22,7 +22,7 @@
|
|
|
22
22
|
"./*.css": "./dist/*.css"
|
|
23
23
|
},
|
|
24
24
|
"dependencies": {
|
|
25
|
-
"@mirrordown/core": "^0.
|
|
25
|
+
"@mirrordown/core": "^0.2.0",
|
|
26
26
|
"unist-util-visit": "^5.1.0"
|
|
27
27
|
},
|
|
28
28
|
"devDependencies": {
|