prosemirror-model - npm Package Versions

1.9.0 (2020-01-07)

New features

The NodeType method hasRequiredAttrs is now public.

Element and attribute names in DOMOutputSpec structures can now contain namespaces.

1.8.2 (2019-11-20)

Bug fixes

Rename ES module files to use a .js extension, since Webpack gets confused by .mjs

1.8.1 (2019-11-19)

Bug fixes

The file referred to in the package's module field now is compiled down to ES5.

1.8.0 (2019-11-08)

New features

Add a module field to package json file.

Add a module field to package json file.

Add a module field to package json file.

Add a module field to package json file.

Add a module field to package json file.

Add a module field to package json file.

Add a module field to package json file.

Add a module field to package json file.

Add a module field to package json file.

Add a module field to package json file.

Add a module field to package json file.

Add a module field to package json file.

Add a module field to package json file.

Add a module field to package json file.

Add a module field to package json file.

Add a module field to package json file.

Add a module field to package json file.

1.7.5 (2019-11-07)

Bug fixes

ContentMatch.edge now throws, as it is supposed to, when you try to access the edge past the last one.

1.7.4 (2019-10-10)

Bug fixes

Fix an issue where fillBefore would in some cases insert unneccesary optional child nodes in the generated content.

1.7.3 (2019-10-03)

Bug fixes

Fix an issue where any whitespace (not just the characters that HTML collapses) was collapsed by the parser in non-whitespace-preserving mode.

1.7.2 (2019-09-04)

Bug fixes

When <br> DOM nodes can't be parsed normally, the parser now converts them to newlines. This should improve parsing of some forms of source code HTML.

1.7.1 (2019-05-31)

Bug fixes

Using Fragment.from on an invalid value, including a Fragment instance from a different version/instance of the library, now raises a meaningful error rather than getting confused.

Fix a bug in parsing overlapping marks of the same non-self-exclusive type.

1.7.0 (2019-01-29)

New features

Mark specs now support a property spanning which, when set to false, prevents the mark's DOM markup from spanning multiple nodes, so that a separate wrapper is created for each adjacent marked node.