@depup/prosemirror-markdown 1.13.4-depup.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/.tern-project ADDED
@@ -0,0 +1,8 @@
1
+ {
2
+ "libs": ["browser"],
3
+ "plugins": {
4
+ "node": {},
5
+ "complete_strings": {},
6
+ "es_modules": {}
7
+ }
8
+ }
package/CHANGELOG.md ADDED
@@ -0,0 +1,311 @@
1
+ ## 1.13.4 (2026-02-04)
2
+
3
+ ### Bug fixes
4
+
5
+ Fix a regression that caused the serializer to crash when a block ends in a hard break.
6
+
7
+ ## 1.13.3 (2026-01-20)
8
+
9
+ ### Bug fixes
10
+
11
+ Properly move trailing whitespace out of marks when they end in a hard break node.
12
+
13
+ ## 1.13.2 (2025-03-18)
14
+
15
+ ### Bug fixes
16
+
17
+ Add a `code` flag to the code mark.
18
+
19
+ ## 1.13.1 (2024-09-26)
20
+
21
+ ### Bug fixes
22
+
23
+ Fix a type error caused by use of an older markdown-it type package.
24
+
25
+ ## 1.13.0 (2024-05-20)
26
+
27
+ ### Bug fixes
28
+
29
+ Fix the type of `MarkdownParser.parse` to be non-nullable. Add a strict option to MarkdownSerializer
30
+
31
+ ### New features
32
+
33
+ The new `strict` option to `MarkdownSerializer` makes it possible to make the serializer ignore node and mark types it doesn't know.
34
+
35
+ ## 1.12.0 (2023-12-11)
36
+
37
+ ### Bug fixes
38
+
39
+ Block-level markup inside a heading is no longer escaped by the serializer.
40
+
41
+ Do not backslash-escape a `+` at the start of line when it isn't followed by a space. Upgrade to markdown-it 14
42
+
43
+ ### New features
44
+
45
+ `MarkdownSerializerState.renderInline` now takes a parameter that controls whether block-level markup should be escaped.
46
+
47
+ Upgrade to markdown-it version 14, which provides ES modules.
48
+
49
+ ## 1.11.2 (2023-08-04)
50
+
51
+ ### Bug fixes
52
+
53
+ Fix some unnecessary escapes for period characters in Markdown serialization.
54
+
55
+ Only escape `#` signs if they would otherwise create a heading. Add a test for headings in list items
56
+
57
+ Fix a bug in `MarkdownSerializer` that broken expelling of whitespace from marks when the mark spanned multiple nodes.
58
+
59
+ ## 1.11.1 (2023-06-30)
60
+
61
+ ### Bug fixes
62
+
63
+ Allow any blocks as first child of list items to align with what Markdown itself does.
64
+
65
+ Add parse rules that clear `strong` and `em` marks when inline CSS resets it.
66
+
67
+ ## 1.11.0 (2023-05-17)
68
+
69
+ ### Bug fixes
70
+
71
+ Make sure blank lines at the end of code blocks are properly serialized.
72
+
73
+ Convert soft breaks (single newlines) in Markdown to spaces, rather than newlines in the ProseMirror document, because newlines tend to behave awkwardly in the editor.
74
+
75
+ Fix a bug that cause the object passed as configuration to `MarkdownSerializer` to be mutated. Add release note
76
+
77
+ Include CommonJS type declarations in the package to please new TypeScript resolution settings.
78
+
79
+ ### New features
80
+
81
+ A new option to `MarkdownSerializer` allows client code to configure which node type should be treated as hard breaks during mark serialization. Remove the extra left bracket
82
+
83
+ ## 1.10.1 (2022-10-28)
84
+
85
+ ### Bug fixes
86
+
87
+ Don't treat the empty string the same as `null` in `wrapBlock`'s `firstDelim` argument. Check content of code blocks for any sequence of backticks
88
+
89
+ Use longer sequences of backticks when serializing a code block that contains three or more backticks in a row.
90
+
91
+ ## 1.10.0 (2022-10-05)
92
+
93
+ ### New features
94
+
95
+ You can now pass an optional markdown-it environment object to .
96
+
97
+ ## 1.9.4 (2022-08-19)
98
+
99
+ ### Bug fixes
100
+
101
+ Don't escape colon characters at the start of a line.
102
+
103
+ Escape parentheses in images and links.
104
+
105
+ Allow links to wrap emphasis markers when serializing Markdown.
106
+
107
+ ## 1.9.3 (2022-07-05)
108
+
109
+ ### Bug fixes
110
+
111
+ Make sure '\!' characters in front of links are escaped.
112
+
113
+ ## 1.9.2 (2022-07-04)
114
+
115
+ ### Bug fixes
116
+
117
+ Don't escape characters in autolinks.
118
+
119
+ Fix a bug that caused the serializer to not escape start-of-line markup when inside a list.
120
+
121
+ ## 1.9.1 (2022-06-02)
122
+
123
+ ### Bug fixes
124
+
125
+ Fix a bug where inline nodes with content would reset the marks in their parent node during Markdown parsing.
126
+
127
+ ## 1.9.0 (2022-05-30)
128
+
129
+ ### New features
130
+
131
+ Include TypeScript type declarations.
132
+
133
+ ## 1.8.0 (2022-03-14)
134
+
135
+ ### New features
136
+
137
+ `MarkdownSerializer` now takes an `escapeExtraCharacters` option that can be used to control backslash-escaping behavior. Fix types for new option
138
+
139
+ ## 1.7.1 (2022-02-16)
140
+
141
+ ### Bug fixes
142
+
143
+ Avoid escaping underscores surrounded by word characters.
144
+
145
+ ## 1.7.0 (2022-01-06)
146
+
147
+ ### New features
148
+
149
+ Upgrade markdown-it to version 12.
150
+
151
+ ## 1.6.2 (2022-01-04)
152
+
153
+ ### Bug fixes
154
+
155
+ Fix a bug where URL text in links and images was overzealously escaped.
156
+
157
+ ## 1.6.1 (2021-12-16)
158
+
159
+ ### Bug fixes
160
+
161
+ Fix a bug where `MarkdownParser.parse` could return null when the parsed content doesn't fit the schema.
162
+
163
+ Make sure underscores are escaped when serializing to Markdown.
164
+
165
+ ## 1.6.0 (2021-09-21)
166
+
167
+ ### New features
168
+
169
+ `MarkdownParser.tokenizer` is now public, for easier creation of parsers that base on other parsers.
170
+
171
+ ## 1.5.2 (2021-09-03)
172
+
173
+ ### Bug fixes
174
+
175
+ Serializing to Markdown now properly escapes '>' characters at the start of the line.
176
+
177
+ ## 1.5.1 (2021-01-06)
178
+
179
+ ### Bug fixes
180
+
181
+ The Markdown parser will now correctly set the `tight` attribute on list nodes.
182
+
183
+ ## 1.5.0 (2020-07-17)
184
+
185
+ ### New features
186
+
187
+ Markdown parse specs can now be specified as `noCloseToken`, which will cause the parser to treat them as a single token, rather than a pair of `_open`/`_close` tokens.
188
+
189
+ ## 1.4.5 (2020-05-14)
190
+
191
+ ### Bug fixes
192
+
193
+ Don't allow hard_break nodes in headings.
194
+
195
+ ## 1.4.4 (2019-12-19)
196
+
197
+ ### Bug fixes
198
+
199
+ Fix issue that broke parsing ordered lists with a starting number other than 1.
200
+
201
+ ## 1.4.3 (2019-12-17)
202
+
203
+ ### Bug fixes
204
+
205
+ Don't use short-hand angle bracket syntax when outputting self-linking URLs that are relative.
206
+
207
+ ## 1.4.2 (2019-11-20)
208
+
209
+ ### Bug fixes
210
+
211
+ Rename ES module files to use a .js extension, since Webpack gets confused by .mjs
212
+
213
+ ## 1.4.1 (2019-11-19)
214
+
215
+ ### Bug fixes
216
+
217
+ The file referred to in the package's `module` field now is compiled down to ES5.
218
+
219
+ ## 1.4.0 (2019-11-08)
220
+
221
+ ### New features
222
+
223
+ Add a `module` field to package json file.
224
+
225
+ ## 1.3.2 (2019-10-30)
226
+
227
+ ### Bug fixes
228
+
229
+ Code blocks in the schema no longer allow marks inside them.
230
+
231
+ Code blocks are now parsed with `preserveWhiteSpace: full`, preventing removal of newline characters.
232
+
233
+ ## 1.3.1 (2019-06-08)
234
+
235
+ ### Bug fixes
236
+
237
+ Fix a bug that could occur when parsing multiple adjacent pieces of text with the same style.
238
+
239
+ ## 1.3.0 (2019-01-22)
240
+
241
+ ### Bug fixes
242
+
243
+ Inline code containing backticks is now serialized wrapped in the appropriate amount of backticks.
244
+
245
+ ### New features
246
+
247
+ The serializer now serializes links whose target is the same as their text content using \< \> syntax.
248
+
249
+ Mark opening and close string callbacks now get passed the mark's context (parent fragment and index).
250
+
251
+ ## 1.2.2 (2018-11-22)
252
+
253
+ ### Bug fixes
254
+
255
+ Hard breaks at the end of an emphasized or strong mark are no longer serialized to invalid Markdown text.
256
+
257
+ ## 1.2.1 (2018-10-19)
258
+
259
+ ### Bug fixes
260
+
261
+ Fixes a bug where inline mark delimiters were serialized incorrectly (the closing and opening marks were swapped, which was only noticeable when they are different).
262
+
263
+ ## 1.2.0 (2018-10-08)
264
+
265
+ ### Bug fixes
266
+
267
+ Fixes an issue where the Markdown serializer would escape special characters in inline code.
268
+
269
+ ### New features
270
+
271
+ Upgrade the markdown-it dependency to version 8.
272
+
273
+ ## 1.1.1 (2018-07-08)
274
+
275
+ ### Bug fixes
276
+
277
+ Fix bug that caused superfluous backslashes to be inserted at the start of some lines when serializing to Markdown.
278
+
279
+ ## 1.1.0 (2018-06-20)
280
+
281
+ ### New features
282
+
283
+ You can now override the handling of softbreak tokens in a custom handler.
284
+
285
+ ## 1.0.4 (2018-04-17)
286
+
287
+ ### Bug fixes
288
+
289
+ Fix crash when serializing marks with line breaks inside of them.
290
+
291
+ ## 1.0.3 (2018-01-10)
292
+
293
+ ### Bug fixes
294
+
295
+ Fix dependency version range for prosemirror-model.
296
+
297
+ ## 1.0.2 (2017-12-07)
298
+
299
+ ### Bug fixes
300
+
301
+ Code blocks are always wrapped in triple backticks when serializing, to avoid parsing corner cases around indented code blocks.
302
+
303
+ ## 1.0.1 (2017-11-05)
304
+
305
+ ### Bug fixes
306
+
307
+ Link marks are now non-inclusive (typing after them produces non-linked text).
308
+
309
+ ## 1.0.0 (2017-10-13)
310
+
311
+ First stable release.
@@ -0,0 +1,100 @@
1
+ # How to contribute
2
+
3
+ - [Getting help](#getting-help)
4
+ - [Submitting bug reports](#submitting-bug-reports)
5
+ - [Contributing code](#contributing-code)
6
+
7
+ ## Getting help
8
+
9
+ Community discussion, questions, and informal bug reporting is done on the
10
+ [discuss.ProseMirror forum](http://discuss.prosemirror.net).
11
+
12
+ ## Submitting bug reports
13
+
14
+ Report bugs on the
15
+ [GitHub issue tracker](http://github.com/prosemirror/prosemirror/issues).
16
+ Before reporting a bug, please read these pointers.
17
+
18
+ - The issue tracker is for *bugs*, not requests for help. Questions
19
+ should be asked on the [forum](http://discuss.prosemirror.net).
20
+
21
+ - Include information about the version of the code that exhibits the
22
+ problem. For browser-related issues, include the browser and browser
23
+ version on which the problem occurred.
24
+
25
+ - Mention very precisely what went wrong. "X is broken" is not a good
26
+ bug report. What did you expect to happen? What happened instead?
27
+ Describe the exact steps a maintainer has to take to make the
28
+ problem occur. A screencast can be useful, but is no substitute for
29
+ a textual description.
30
+
31
+ - A great way to make it easy to reproduce your problem, if it can not
32
+ be trivially reproduced on the website demos, is to submit a script
33
+ that triggers the issue.
34
+
35
+ ## Contributing code
36
+
37
+ - Make sure you have a [GitHub Account](https://github.com/signup/free)
38
+
39
+ - Fork the relevant repository
40
+ ([how to fork a repo](https://help.github.com/articles/fork-a-repo))
41
+
42
+ - Create a local checkout of the code. You can use the
43
+ [main repository](https://github.com/prosemirror/prosemirror) to
44
+ easily check out all core modules.
45
+
46
+ - Make your changes, and commit them
47
+
48
+ - Follow the code style of the rest of the project (see below). Run
49
+ `npm run lint` (in the main repository checkout) to make sure that
50
+ the linter is happy.
51
+
52
+ - If your changes are easy to test or likely to regress, add tests in
53
+ the relevant `test/` directory. Either put them in an existing
54
+ `test-*.js` file, if they fit there, or add a new file.
55
+
56
+ - Make sure all tests pass. Run `npm run test` to verify tests pass
57
+ (you will need Node.js v6+).
58
+
59
+ - Submit a pull request ([how to create a pull request](https://help.github.com/articles/fork-a-repo)).
60
+ Don't put more than one feature/fix in a single pull request.
61
+
62
+ By contributing code to ProseMirror you
63
+
64
+ - Agree to license the contributed code under the project's [MIT
65
+ license](https://github.com/ProseMirror/prosemirror/blob/master/LICENSE).
66
+
67
+ - Confirm that you have the right to contribute and license the code
68
+ in question. (Either you hold all rights on the code, or the rights
69
+ holder has explicitly granted the right to use it like this,
70
+ through a compatible open source license or through a direct
71
+ agreement with you.)
72
+
73
+ ### Coding standards
74
+
75
+ - ES6 syntax, targeting an ES5 runtime (i.e. don't use library
76
+ elements added by ES6, don't use ES7/ES.next syntax).
77
+
78
+ - 2 spaces per indentation level, no tabs.
79
+
80
+ - No semicolons except when necessary.
81
+
82
+ - Follow the surrounding code when it comes to spacing, brace
83
+ placement, etc.
84
+
85
+ - Brace-less single-statement bodies are encouraged (whenever they
86
+ don't impact readability).
87
+
88
+ - [getdocs](https://github.com/marijnh/getdocs)-style doc comments
89
+ above items that are part of the public API.
90
+
91
+ - When documenting non-public items, you can put the type after a
92
+ single colon, so that getdocs doesn't pick it up and add it to the
93
+ API reference.
94
+
95
+ - The linter (`npm run lint`) complains about unused variables and
96
+ functions. Prefix their names with an underscore to muffle it.
97
+
98
+ - ProseMirror does *not* follow JSHint or JSLint prescribed style.
99
+ Patches that try to 'fix' code to pass one of these linters will not
100
+ be accepted.
package/LICENSE ADDED
@@ -0,0 +1,19 @@
1
+ Copyright (C) 2015-2017 by Marijn Haverbeke <marijn@haverbeke.berlin> and others
2
+
3
+ Permission is hereby granted, free of charge, to any person obtaining a copy
4
+ of this software and associated documentation files (the "Software"), to deal
5
+ in the Software without restriction, including without limitation the rights
6
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
7
+ copies of the Software, and to permit persons to whom the Software is
8
+ furnished to do so, subject to the following conditions:
9
+
10
+ The above copyright notice and this permission notice shall be included in
11
+ all copies or substantial portions of the Software.
12
+
13
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
14
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
15
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
16
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
17
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
18
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
19
+ THE SOFTWARE.
package/README.md ADDED
@@ -0,0 +1,33 @@
1
+ # @depup/prosemirror-markdown
2
+
3
+ > Dependency-bumped version of [prosemirror-markdown](https://www.npmjs.com/package/prosemirror-markdown)
4
+
5
+ Generated by [DepUp](https://github.com/depup/npm) -- all production
6
+ dependencies bumped to latest versions.
7
+
8
+ ## Installation
9
+
10
+ ```bash
11
+ npm install @depup/prosemirror-markdown
12
+ ```
13
+
14
+ | Field | Value |
15
+ |-------|-------|
16
+ | Original | [prosemirror-markdown](https://www.npmjs.com/package/prosemirror-markdown) @ 1.13.4 |
17
+ | Processed | 2026-03-17 |
18
+ | Smoke test | passed |
19
+ | Deps updated | 3 |
20
+
21
+ ## Dependency Changes
22
+
23
+ | Dependency | From | To |
24
+ |------------|------|-----|
25
+ | @types/markdown-it | ^14.0.0 | ^14.1.2 |
26
+ | markdown-it | ^14.0.0 | ^14.1.1 |
27
+ | prosemirror-model | ^1.25.0 | ^1.25.4 |
28
+
29
+ ---
30
+
31
+ Source: https://github.com/depup/npm | Original: https://www.npmjs.com/package/prosemirror-markdown
32
+
33
+ License inherited from the original package.
package/changes.json ADDED
@@ -0,0 +1,18 @@
1
+ {
2
+ "bumped": {
3
+ "markdown-it": {
4
+ "from": "^14.0.0",
5
+ "to": "^14.1.1"
6
+ },
7
+ "prosemirror-model": {
8
+ "from": "^1.25.0",
9
+ "to": "^1.25.4"
10
+ },
11
+ "@types/markdown-it": {
12
+ "from": "^14.0.0",
13
+ "to": "^14.1.2"
14
+ }
15
+ },
16
+ "timestamp": "2026-03-17T16:38:05.839Z",
17
+ "totalUpdated": 3
18
+ }