@osdlc/markdown-link 0.0.0-stage → 0.5.0

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 ADDED
@@ -0,0 +1,7 @@
1
+ # @osdlc/markdown-link
2
+
3
+ ## 0.5.0
4
+
5
+ ### Minor Changes
6
+
7
+ - 5aecf76: First release. The TypeScript twin of the parsing half of the Rust `markdown-link` crate, with no dependencies: `stripCode` and `stripCodeWith`, the code lexer under CommonMark and skill-export rules; `parseInner` and `targetRange` for one wikilink body; `isVaultLinkUrl` and `mdLinkTarget` for markdown link URLs; `bodyLinksSpanned` and `bodyLinks`, which find every wikilink, embed and relative markdown link in a body, each with its `alias`; `displayText`, which shows each link as a reader sees it; `parseTypedRef` for a whole `[[type/slug|Alias]]` value; and `ATTACHMENT_EXTENSIONS`. Spans and ranges are UTF-16 offsets. Its tests read the crate's `tests/fixtures/conformance.json`, so the two agree on every case in it.
@@ -0,0 +1,64 @@
1
+ # Contributing
2
+
3
+ Thanks for your interest in `@osdlc/markdown-link`.
4
+
5
+ ## Issues
6
+
7
+ Report bugs and ask for features in the
8
+ [issue tracker](https://github.com/osdlc/osdlc/issues). For a bug, include the
9
+ library version, your runtime and its version, and the note text that
10
+ misbehaves. Report security problems privately. See
11
+ [SECURITY.md](./SECURITY.md).
12
+
13
+ ## Pull requests
14
+
15
+ This package lives in [osdlc/osdlc](https://github.com/osdlc/osdlc) under
16
+ `packages/ts/markdown-link`. Open pull requests there. They are reviewed and
17
+ merged there.
18
+
19
+ ## Running the tests
20
+
21
+ The repository is a pnpm workspace. Install from the repository root, then
22
+ work in the package directory. The tests run on [Vitest](https://vitest.dev)
23
+ under Node 22.12 or later.
24
+
25
+ ```sh
26
+ pnpm install
27
+ cd packages/ts/markdown-link
28
+ pnpm test
29
+ ```
30
+
31
+ `pnpm run coverage` reports test coverage. It sets no threshold.
32
+
33
+ `pnpm run build` compiles the package to `dist/`. `pnpm run smoke` runs
34
+ `tests/smoke.mjs`, a short check of the built package under Node. Build first.
35
+ It is not published.
36
+
37
+ Other checks:
38
+
39
+ ```sh
40
+ pnpm run typecheck
41
+ pnpm run lint
42
+ pnpm run format:check
43
+ ```
44
+
45
+ ## The case file
46
+
47
+ `packages/rust/markdown-link/tests/fixtures/conformance.json` is read by this
48
+ package's `tests/conformance.test.ts` and by the Rust crate's
49
+ `tests/conformance.rs`. A new case goes into that file, so both suites cover
50
+ it. A change to the parsing behaviour lands in both packages in one pull
51
+ request.
52
+
53
+ ## Code style
54
+
55
+ - TypeScript, ES modules, and explicit `.ts` import paths.
56
+ - Prettier formats the code and oxlint checks it. Run `pnpm run format` and
57
+ `pnpm run lint` before you commit.
58
+ - Add a test for each behaviour change or bug fix.
59
+ - A new export gets TSDoc, a use in `examples/`, which imports the package by
60
+ name, and a mention in the README.
61
+ - For a change users can see, add a changeset: run `pnpm changeset` at the
62
+ repository root. Start a breaking change's summary with `**Breaking:**`.
63
+ Do not edit `CHANGELOG.md` or `version` by hand. The release writes them.
64
+ See [packages/README.md](https://github.com/osdlc/osdlc/blob/main/packages/README.md).
package/LICENSE-APACHE ADDED
@@ -0,0 +1,202 @@
1
+
2
+ Apache License
3
+ Version 2.0, January 2004
4
+ http://www.apache.org/licenses/
5
+
6
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
7
+
8
+ 1. Definitions.
9
+
10
+ "License" shall mean the terms and conditions for use, reproduction,
11
+ and distribution as defined by Sections 1 through 9 of this document.
12
+
13
+ "Licensor" shall mean the copyright owner or entity authorized by
14
+ the copyright owner that is granting the License.
15
+
16
+ "Legal Entity" shall mean the union of the acting entity and all
17
+ other entities that control, are controlled by, or are under common
18
+ control with that entity. For the purposes of this definition,
19
+ "control" means (i) the power, direct or indirect, to cause the
20
+ direction or management of such entity, whether by contract or
21
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
22
+ outstanding shares, or (iii) beneficial ownership of such entity.
23
+
24
+ "You" (or "Your") shall mean an individual or Legal Entity
25
+ exercising permissions granted by this License.
26
+
27
+ "Source" form shall mean the preferred form for making modifications,
28
+ including but not limited to software source code, documentation
29
+ source, and configuration files.
30
+
31
+ "Object" form shall mean any form resulting from mechanical
32
+ transformation or translation of a Source form, including but
33
+ not limited to compiled object code, generated documentation,
34
+ and conversions to other media types.
35
+
36
+ "Work" shall mean the work of authorship, whether in Source or
37
+ Object form, made available under the License, as indicated by a
38
+ copyright notice that is included in or attached to the work
39
+ (an example is provided in the Appendix below).
40
+
41
+ "Derivative Works" shall mean any work, whether in Source or Object
42
+ form, that is based on (or derived from) the Work and for which the
43
+ editorial revisions, annotations, elaborations, or other modifications
44
+ represent, as a whole, an original work of authorship. For the purposes
45
+ of this License, Derivative Works shall not include works that remain
46
+ separable from, or merely link (or bind by name) to the interfaces of,
47
+ the Work and Derivative Works thereof.
48
+
49
+ "Contribution" shall mean any work of authorship, including
50
+ the original version of the Work and any modifications or additions
51
+ to that Work or Derivative Works thereof, that is intentionally
52
+ submitted to Licensor for inclusion in the Work by the copyright owner
53
+ or by an individual or Legal Entity authorized to submit on behalf of
54
+ the copyright owner. For the purposes of this definition, "submitted"
55
+ means any form of electronic, verbal, or written communication sent
56
+ to the Licensor or its representatives, including but not limited to
57
+ communication on electronic mailing lists, source code control systems,
58
+ and issue tracking systems that are managed by, or on behalf of, the
59
+ Licensor for the purpose of discussing and improving the Work, but
60
+ excluding communication that is conspicuously marked or otherwise
61
+ designated in writing by the copyright owner as "Not a Contribution."
62
+
63
+ "Contributor" shall mean Licensor and any individual or Legal Entity
64
+ on behalf of whom a Contribution has been received by Licensor and
65
+ subsequently incorporated within the Work.
66
+
67
+ 2. Grant of Copyright License. Subject to the terms and conditions of
68
+ this License, each Contributor hereby grants to You a perpetual,
69
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
70
+ copyright license to reproduce, prepare Derivative Works of,
71
+ publicly display, publicly perform, sublicense, and distribute the
72
+ Work and such Derivative Works in Source or Object form.
73
+
74
+ 3. Grant of Patent License. Subject to the terms and conditions of
75
+ this License, each Contributor hereby grants to You a perpetual,
76
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77
+ (except as stated in this section) patent license to make, have made,
78
+ use, offer to sell, sell, import, and otherwise transfer the Work,
79
+ where such license applies only to those patent claims licensable
80
+ by such Contributor that are necessarily infringed by their
81
+ Contribution(s) alone or by combination of their Contribution(s)
82
+ with the Work to which such Contribution(s) was submitted. If You
83
+ institute patent litigation against any entity (including a
84
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
85
+ or a Contribution incorporated within the Work constitutes direct
86
+ or contributory patent infringement, then any patent licenses
87
+ granted to You under this License for that Work shall terminate
88
+ as of the date such litigation is filed.
89
+
90
+ 4. Redistribution. You may reproduce and distribute copies of the
91
+ Work or Derivative Works thereof in any medium, with or without
92
+ modifications, and in Source or Object form, provided that You
93
+ meet the following conditions:
94
+
95
+ (a) You must give any other recipients of the Work or
96
+ Derivative Works a copy of this License; and
97
+
98
+ (b) You must cause any modified files to carry prominent notices
99
+ stating that You changed the files; and
100
+
101
+ (c) You must retain, in the Source form of any Derivative Works
102
+ that You distribute, all copyright, patent, trademark, and
103
+ attribution notices from the Source form of the Work,
104
+ excluding those notices that do not pertain to any part of
105
+ the Derivative Works; and
106
+
107
+ (d) If the Work includes a "NOTICE" text file as part of its
108
+ distribution, then any Derivative Works that You distribute must
109
+ include a readable copy of the attribution notices contained
110
+ within such NOTICE file, excluding those notices that do not
111
+ pertain to any part of the Derivative Works, in at least one
112
+ of the following places: within a NOTICE text file distributed
113
+ as part of the Derivative Works; within the Source form or
114
+ documentation, if provided along with the Derivative Works; or,
115
+ within a display generated by the Derivative Works, if and
116
+ wherever such third-party notices normally appear. The contents
117
+ of the NOTICE file are for informational purposes only and
118
+ do not modify the License. You may add Your own attribution
119
+ notices within Derivative Works that You distribute, alongside
120
+ or as an addendum to the NOTICE text from the Work, provided
121
+ that such additional attribution notices cannot be construed
122
+ as modifying the License.
123
+
124
+ You may add Your own copyright statement to Your modifications and
125
+ may provide additional or different license terms and conditions
126
+ for use, reproduction, or distribution of Your modifications, or
127
+ for any such Derivative Works as a whole, provided Your use,
128
+ reproduction, and distribution of the Work otherwise complies with
129
+ the conditions stated in this License.
130
+
131
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
132
+ any Contribution intentionally submitted for inclusion in the Work
133
+ by You to the Licensor shall be under the terms and conditions of
134
+ this License, without any additional terms or conditions.
135
+ Notwithstanding the above, nothing herein shall supersede or modify
136
+ the terms of any separate license agreement you may have executed
137
+ with Licensor regarding such Contributions.
138
+
139
+ 6. Trademarks. This License does not grant permission to use the trade
140
+ names, trademarks, service marks, or product names of the Licensor,
141
+ except as required for reasonable and customary use in describing the
142
+ origin of the Work and reproducing the content of the NOTICE file.
143
+
144
+ 7. Disclaimer of Warranty. Unless required by applicable law or
145
+ agreed to in writing, Licensor provides the Work (and each
146
+ Contributor provides its Contributions) on an "AS IS" BASIS,
147
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
148
+ implied, including, without limitation, any warranties or conditions
149
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
150
+ PARTICULAR PURPOSE. You are solely responsible for determining the
151
+ appropriateness of using or redistributing the Work and assume any
152
+ risks associated with Your exercise of permissions under this License.
153
+
154
+ 8. Limitation of Liability. In no event and under no legal theory,
155
+ whether in tort (including negligence), contract, or otherwise,
156
+ unless required by applicable law (such as deliberate and grossly
157
+ negligent acts) or agreed to in writing, shall any Contributor be
158
+ liable to You for damages, including any direct, indirect, special,
159
+ incidental, or consequential damages of any character arising as a
160
+ result of this License or out of the use or inability to use the
161
+ Work (including but not limited to damages for loss of goodwill,
162
+ work stoppage, computer failure or malfunction, or any and all
163
+ other commercial damages or losses), even if such Contributor
164
+ has been advised of the possibility of such damages.
165
+
166
+ 9. Accepting Warranty or Additional Liability. While redistributing
167
+ the Work or Derivative Works thereof, You may choose to offer,
168
+ and charge a fee for, acceptance of support, warranty, indemnity,
169
+ or other liability obligations and/or rights consistent with this
170
+ License. However, in accepting such obligations, You may act only
171
+ on Your own behalf and on Your sole responsibility, not on behalf
172
+ of any other Contributor, and only if You agree to indemnify,
173
+ defend, and hold each Contributor harmless for any liability
174
+ incurred by, or claims asserted against, such Contributor by reason
175
+ of your accepting any such warranty or additional liability.
176
+
177
+ END OF TERMS AND CONDITIONS
178
+
179
+ APPENDIX: How to apply the Apache License to your work.
180
+
181
+ To apply the Apache License to your work, attach the following
182
+ boilerplate notice, with the fields enclosed by brackets "[]"
183
+ replaced with your own identifying information. (Don't include
184
+ the brackets!) The text should be enclosed in the appropriate
185
+ comment syntax for the file format. We also recommend that a
186
+ file or class name and description of purpose be included on the
187
+ same "printed page" as the copyright notice for easier
188
+ identification within third-party archives.
189
+
190
+ Copyright 2026 Sizer LLC
191
+
192
+ Licensed under the Apache License, Version 2.0 (the "License");
193
+ you may not use this file except in compliance with the License.
194
+ You may obtain a copy of the License at
195
+
196
+ http://www.apache.org/licenses/LICENSE-2.0
197
+
198
+ Unless required by applicable law or agreed to in writing, software
199
+ distributed under the License is distributed on an "AS IS" BASIS,
200
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
201
+ See the License for the specific language governing permissions and
202
+ limitations under the License.
package/LICENSE-MIT ADDED
@@ -0,0 +1,21 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2026 sksizer
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.
package/README.md CHANGED
@@ -1,3 +1,114 @@
1
- # Temporary Holding Version
1
+ # @osdlc/markdown-link
2
2
 
3
- This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
3
+ Wikilink parsing that follows documented link-resolution conventions, with no dependencies. It is
4
+ the TypeScript twin of the parsing half of the Rust
5
+ [`markdown-link`](https://crates.io/crates/markdown-link) crate, which sits beside it in
6
+ [`packages/rust/markdown-link`](https://github.com/osdlc/osdlc/tree/main/packages/rust/markdown-link).
7
+ Each function gives the same answer as its Rust namesake.
8
+
9
+ Resolution (`LinkIndex`) is not here yet.
10
+
11
+ ## Why
12
+
13
+ Notes link to each other with `[[Note]]`, `[[Note#Heading|alias]]`,
14
+ `![[image.png]]` and relative markdown links. A tool that builds a link graph,
15
+ indexes a folder of notes or rewrites links on a rename must find every one of
16
+ them, skip the ones inside code, and know exactly where each sits in the text.
17
+ A regular expression gets code spans, escaped pipes and embed sizes wrong.
18
+
19
+ This package finds them with the same rules as the Rust crate, so a TypeScript
20
+ tool and a Rust tool that read the same notes agree on every link.
21
+
22
+ ## Who it is for
23
+
24
+ Programs that read or change a folder of notes in TypeScript: link graph
25
+ builders, search indexers, renderers, linters and rename tools.
26
+
27
+ ## When not to use it
28
+
29
+ - You render markdown with remark or micromark and only want wikilinks turned
30
+ into links. A remark or micromark wikilink plugin fits the pipeline better.
31
+ - You need a full markdown parser or an editor model. This package only finds
32
+ links and blanks code.
33
+ - You need to resolve a link to a file. That is the Rust crate's `LinkIndex`,
34
+ which has no TypeScript twin yet.
35
+
36
+ ## How it compares
37
+
38
+ - remark and micromark plugins, such as
39
+ [`@moritzrs/micromark-extension-ofm-wikilink`](https://www.npmjs.com/package/@moritzrs/micromark-extension-ofm-wikilink)
40
+ and
41
+ [`@sgawarat/remark-obsidian-wikilink`](https://www.npmjs.com/package/@sgawarat/remark-obsidian-wikilink),
42
+ parse wikilinks as part of a markdown syntax tree. They need the unified
43
+ toolchain, and they do not share a case file with a Rust implementation.
44
+ - This package works on the plain text, with no dependencies. It returns spans
45
+ into the original string, so a caller can rewrite a link in place.
46
+ - The same author's Rust [`markdown-link`](https://crates.io/crates/markdown-link)
47
+ crate is the reference. Use it from Rust; use this package from TypeScript.
48
+
49
+ ## Install
50
+
51
+ ```sh
52
+ npm install @osdlc/markdown-link
53
+ ```
54
+
55
+ `pnpm add @osdlc/markdown-link` and `yarn add @osdlc/markdown-link` work too.
56
+
57
+ ## Quick start
58
+
59
+ ```ts
60
+ import { bodyLinksSpanned } from '@osdlc/markdown-link'
61
+
62
+ bodyLinksSpanned('See [[Note#h|alias]] and `[[not a link]]`')
63
+ // [{ kind: 'wikilink', raw: 'Note#h|alias', target: 'Note', alias: 'alias', start: 4, end: 20 }]
64
+ ```
65
+
66
+ ## Exports
67
+
68
+ - Code: `stripCode` blanks fenced and inline code to spaces, keeping every
69
+ `\n` and the code point count, so links in code are not harvested.
70
+ `stripCodeWith(text, rules)` takes `'commonmark'` (the default) or
71
+ `'skill-export'`.
72
+ - One link: `parseInner` splits a wikilink body into target, heading and
73
+ alias; `targetRange` is where the target sits in it.
74
+ - Markdown link URLs: `isVaultLinkUrl` says whether a URL is a note or an
75
+ attachment; `mdLinkTarget` percent-decodes it and drops `.md`.
76
+ - A body: `bodyLinksSpanned` finds every wikilink, embed and relative markdown
77
+ link, with its span; `bodyLinks` is the same scan without spans.
78
+ - Display text: `displayText` replaces each wikilink and embed with what a
79
+ reader sees, its alias or else its target. An embed's `|300` or `|300x200`
80
+ is a size, not text, so `![[img.png|300]]` shows `img.png`.
81
+ - Typed references: `parseTypedRef` reads a whole `[[type/slug]]` or
82
+ `[[type/slug|Alias]]` value into `{ kind, slug, alias }`, or `null`.
83
+ - `ATTACHMENT_EXTENSIONS`: the extensions that count as vault attachments.
84
+
85
+ Spans and ranges are UTF-16 offsets, so `body.slice(start, end)` is the link.
86
+ The Rust crate reports byte offsets.
87
+
88
+ ## Twin
89
+
90
+ The Rust crate `markdown-link` has the parsing functions above under their
91
+ snake_case names. It also resolves links (`LinkIndex`), reads links in
92
+ frontmatter and has smaller helpers, which this package does not have yet.
93
+ Both suites read one case file,
94
+ `packages/rust/markdown-link/tests/fixtures/conformance.json` in the
95
+ repository, so they agree on every case in it.
96
+
97
+ ## Stability
98
+
99
+ This is a 0.x package. Every export is stable in 0.x. No export is
100
+ experimental, beta or alpha, and `tests/stability.test.ts` fails if one is
101
+ tagged so. A breaking change comes only in a new minor version, and the
102
+ CHANGELOG marks it.
103
+
104
+ ## Runtimes and platforms
105
+
106
+ Node.js 22 or later, ESM only. The built package is tested on Node.js 22 and
107
+ 24. The code is ES2022 string handling plus `TextEncoder` and `TextDecoder`,
108
+ with no imports and no DOM, but other runtimes, such as Bun, Deno or a
109
+ browser, are not tested. It has no file system or platform code. Its tests run on Linux
110
+ and macOS.
111
+
112
+ ## Licence
113
+
114
+ `MIT OR Apache-2.0`, at your option. See [LICENSE-MIT](./LICENSE-MIT) and [LICENSE-APACHE](./LICENSE-APACHE).
package/SECURITY.md ADDED
@@ -0,0 +1,23 @@
1
+ # Security policy
2
+
3
+ ## Reporting a vulnerability
4
+
5
+ Please report vulnerabilities privately. Do not open a public issue.
6
+
7
+ Use GitHub private vulnerability reporting on the repository: open the
8
+ [Security tab](https://github.com/osdlc/osdlc/security) and choose
9
+ "Report a vulnerability".
10
+
11
+ Include the version, a short description, and steps to reproduce. A minimal
12
+ code sample helps.
13
+
14
+ ## Supported versions
15
+
16
+ Only the latest release gets security fixes. While the version is 0.x, that
17
+ is the latest minor release. Upgrade to it.
18
+
19
+ ## What to expect
20
+
21
+ This is a small project. We aim to reply within a week. We will tell you
22
+ whether we accept the report and keep you updated until a fix is released.
23
+ We will credit you in the release notes if you want that.
@@ -0,0 +1,64 @@
1
+ /**
2
+ * The body link scanner: every link in a body, with its span. A port of the
3
+ * `markdown-link` crate's `body_links_spanned` and `body_links`.
4
+ */
5
+ /** What syntax produced a `BodyLink`. */
6
+ export type BodyLinkKind = 'wikilink' | 'embed' | 'markdown';
7
+ /** One outgoing reference found in a body, with its span, before resolution. */
8
+ export interface BodyLink {
9
+ kind: BodyLinkKind;
10
+ /**
11
+ * The reference as written between the delimiters, with any code inside it
12
+ * blanked to spaces.
13
+ */
14
+ raw: string;
15
+ /**
16
+ * What resolution runs against. A wikilink's `raw` minus `#heading` /
17
+ * `^block` / `|alias` and the `\` escaping the pipe; a markdown link's URL
18
+ * percent-decoded and minus a trailing `.md`.
19
+ */
20
+ target: string;
21
+ /**
22
+ * A wikilink's or embed's `|alias`: the text after the first `|` outside
23
+ * code, read from the body so code inside it is kept. `null` when there is
24
+ * none or it is empty, and for a markdown link.
25
+ */
26
+ alias: string | null;
27
+ /**
28
+ * UTF-16 offsets of the whole link syntax within the body, so
29
+ * `body.slice(start, end)` is the link. The Rust crate reports byte offsets.
30
+ * An embed's `!` is inside the span.
31
+ */
32
+ start: number;
33
+ end: number;
34
+ }
35
+ /** What kind of reference produced a `RawLink`. */
36
+ export type LinkKind = 'wikilink' | 'embed';
37
+ /** A body reference without its span. */
38
+ export interface RawLink {
39
+ /**
40
+ * What resolution runs against. A wikilink's text minus `#heading`, `|alias`
41
+ * and the `\` escaping the pipe; a markdown link's URL percent-decoded and
42
+ * minus a trailing `.md`.
43
+ */
44
+ target: string;
45
+ kind: LinkKind;
46
+ }
47
+ /**
48
+ * Every wikilink, embed and relative markdown link in a note body, in the
49
+ * order they appear. `bodyLinksSpanned` without the spans, so the two cannot
50
+ * disagree. A markdown link is reported as `'wikilink'`.
51
+ */
52
+ export declare function bodyLinks(body: string): RawLink[];
53
+ /**
54
+ * Every wikilink, embed and relative markdown link in a body, in encounter
55
+ * order, with spans.
56
+ *
57
+ * Code is blanked before matching, `[[` never nests, and a markdown link
58
+ * counts only when `isVaultLinkUrl` accepts its URL and it carries no scheme.
59
+ *
60
+ * The scan walks code points. `stripCode` keeps the code point count of its
61
+ * input, not its UTF-16 length, so a code point index into the stripped text
62
+ * is one into the body, and a table converts it to a UTF-16 offset.
63
+ */
64
+ export declare function bodyLinksSpanned(body: string): BodyLink[];