Releases · rasendubi/uniorg

19 May 01:15

uniorg@1.2.0

#109 dbf6452 Thanks @rasendubi! - Support export-snippet in uniorg, uniorg-parse, uniorg-rehype, and uniorg-stringify.

export-snippet has the following form: @@backend:value@@. Example: @@html:@@some text@@html:.

This is a breaking change for uniorg-parse as it may output nodes unknown to downstream users (uniorg-rehype and uniorg-stringify). If you upgrade uniorg-parse, you should also upgrade uniorg-rehype and uniorg-stringify to the corresponding versions.
#111 b45baf9 Thanks @rasendubi! - Support line-break in uniorg, uniorg-parse, uniorg-rehype, and uniorg-stringify.

This is a breaking change for uniorg-parse as it may output nodes unknown to downstream users (uniorg-rehype and uniorg-stringify). If you upgrade uniorg-parse, you should also upgrade uniorg-rehype and uniorg-stringify to the corresponding versions.

Assets 2

19 May 01:15

uniorg-stringify@1.3.0

#109 dbf6452 Thanks @rasendubi! - Support export-snippet in uniorg, uniorg-parse, uniorg-rehype, and uniorg-stringify.

export-snippet has the following form: @@backend:value@@. Example: @@html:@@some text@@html:.

This is a breaking change for uniorg-parse as it may output nodes unknown to downstream users (uniorg-rehype and uniorg-stringify). If you upgrade uniorg-parse, you should also upgrade uniorg-rehype and uniorg-stringify to the corresponding versions.
#111 b45baf9 Thanks @rasendubi! - Support line-break in uniorg, uniorg-parse, uniorg-rehype, and uniorg-stringify.

This is a breaking change for uniorg-parse as it may output nodes unknown to downstream users (uniorg-rehype and uniorg-stringify). If you upgrade uniorg-parse, you should also upgrade uniorg-rehype and uniorg-stringify to the corresponding versions.

Assets 2

19 May 01:15

uniorg-rehype@1.2.0

#109 dbf6452 Thanks @rasendubi! - Support export-snippet in uniorg, uniorg-parse, uniorg-rehype, and uniorg-stringify.

export-snippet has the following form: @@backend:value@@. Example: @@html:@@some text@@html:.

This is a breaking change for uniorg-parse as it may output nodes unknown to downstream users (uniorg-rehype and uniorg-stringify). If you upgrade uniorg-parse, you should also upgrade uniorg-rehype and uniorg-stringify to the corresponding versions.
#111 b45baf9 Thanks @rasendubi! - Support line-break in uniorg, uniorg-parse, uniorg-rehype, and uniorg-stringify.

This is a breaking change for uniorg-parse as it may output nodes unknown to downstream users (uniorg-rehype and uniorg-stringify). If you upgrade uniorg-parse, you should also upgrade uniorg-rehype and uniorg-stringify to the corresponding versions.

Assets 2

19 May 08:50

uniorg-parse@3.0.1

#112 0e1d4b7 Thanks @rasendubi! - Allow Zero-Width Space as emphasis separator.

Assets 2

19 May 01:15

uniorg-parse@3.0.0

#109 dbf6452 Thanks @rasendubi! - Support export-snippet in uniorg, uniorg-parse, uniorg-rehype, and uniorg-stringify.

export-snippet has the following form: @@backend:value@@. Example: @@html:@@some text@@html:.

This is a breaking change for uniorg-parse as it may output nodes unknown to downstream users (uniorg-rehype and uniorg-stringify). If you upgrade uniorg-parse, you should also upgrade uniorg-rehype and uniorg-stringify to the corresponding versions.
#111 b45baf9 Thanks @rasendubi! - Support line-break in uniorg, uniorg-parse, uniorg-rehype, and uniorg-stringify.

This is a breaking change for uniorg-parse as it may output nodes unknown to downstream users (uniorg-rehype and uniorg-stringify). If you upgrade uniorg-parse, you should also upgrade uniorg-rehype and uniorg-stringify to the corresponding versions.