@readme/markdown 15.5.0 → 15.5.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/dist/lib/constants.d.ts +2 -0
- package/dist/lib/utils/mdxish/mdxish-expression.d.ts +1 -1
- package/dist/main.js +338 -180
- package/dist/main.node.js +338 -180
- package/dist/main.node.js.map +1 -1
- package/dist/processor/transform/mdxish/repair-mistaken-table-closers.d.ts +1 -1
- package/dist/processor/transform/mdxish/variables-text.d.ts +11 -0
- package/dist/render-fixture.node.js +338 -180
- package/dist/render-fixture.node.js.map +1 -1
- package/package.json +1 -1
package/dist/lib/constants.d.ts
CHANGED
|
@@ -2,6 +2,8 @@
|
|
|
2
2
|
* Pattern to match component tags (PascalCase or snake_case)
|
|
3
3
|
*/
|
|
4
4
|
export declare const componentTagPattern: RegExp;
|
|
5
|
+
/** A bare component name, the same shape `componentTagPattern` accepts inside `<…>`. */
|
|
6
|
+
export declare const componentNamePattern: RegExp;
|
|
5
7
|
/**
|
|
6
8
|
* MDAST flow (block-level) content types that cannot be represented
|
|
7
9
|
* inside GFM table cells. Used to decide whether a table should be
|
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
/**
|
|
2
|
-
* Collect the
|
|
2
|
+
* Collect the component names an expression uses as JSX tags. Parsed rather than pattern
|
|
3
3
|
* matched: `{count < Max ? <Foo/> : <Bar/>}` puts a capitalized name straight after a `<` without
|
|
4
4
|
* it being a tag, and only the parser can tell the two apart. Unparseable input yields nothing —
|
|
5
5
|
* evaluation is about to throw on it anyway.
|