react-markdown 2.0.0 release notes

2.0.0

Breaking signals21 Feb 2016Changelog file

The release increments the stable major version.
1.2.4 → 2.0.0
The changelog explicitly labels a breaking change.
Breaking change: The renderer now requires Node 0.14 or higher. This is because the renderer uses stateless components internally.

Breaking change: The renderer now requires Node 0.14 or higher. This is because the renderer uses stateless components internally.
Breaking change: allowNode now receives different properties in the options argument. See README.md for more details.
Breaking change: CommonMark has changed some type names. Html is now HtmlInline, Header is now Heading and HorizontalRule is now ThematicBreak. This affects the allowedTypes and disallowedTypes options.
Breaking change: A bug in the allowedTypes/disallowedTypes and allowNode options made them only applicable to certain types. In this version, all types are filtered, as expected.
Breaking change: Link URIs are now filtered through an XSS-filter by default, prefixing “dangerous” protocols such as javascript: with x- (eg: javascript:alert('foo') turns into x-javascript:alert('foo')). This can be overridden with the transformLinkUri-option. Pass null to disable the feature or a custom function to replace the built-in behaviour.

Breaking signals21 Feb 2016Changelog file

The release increments the stable major version.
1.2.4 → 2.0.0
The changelog explicitly labels a breaking change.
Breaking change: The renderer now requires Node 0.14 or higher. This is because the renderer uses stateless components internally.

Breaking change: The renderer now requires Node 0.14 or higher. This is because the renderer uses stateless components internally.
Breaking change: allowNode now receives different properties in the options argument. See README.md for more details.
Breaking change: CommonMark has changed some type names. Html is now HtmlInline, Header is now Heading and HorizontalRule is now ThematicBreak. This affects the allowedTypes and disallowedTypes options.
Breaking change: A bug in the allowedTypes/disallowedTypes and allowNode options made them only applicable to certain types. In this version, all types are filtered, as expected.
Breaking change: Link URIs are now filtered through an XSS-filter by default, prefixing “dangerous” protocols such as javascript: with x- (eg: javascript:alert('foo') turns into x-javascript:alert('foo')). This can be overridden with the transformLinkUri-option. Pass null to disable the feature or a custom function to replace the built-in behaviour.