[email protected]

6.0.1 (2020-03-05)

Note: Version bump only for package babel-plugin-react-intl

@formatjs/[email protected]

1.1.22 (2020-03-05)

Note: Version bump only for package @formatjs/cli

[email protected]

8.0.0 (2020-03-04)

Features

• intl-messageformat: combine formatHTMLMessage into format (d59fbf1)

BREAKING CHANGES

• intl-messageformat: We've modified the way we parse and format embedded
  XML/HTML as follow:

1. formatHTMLMessage has been combined with format
2. All tags specified must have corresponding values and will throw
   error if it's missing, e.g: new IntlMessageFormat("a <b>strong</b>").format({ b: (...chunks) => <strong>chunks</strong> })
3. Self-closing tags are treated as string literal by default. We don't
   allow formatting self-closing tags because we already use ICU
   {placeholder} syntax for that.
4. XML/HTML tags are escaped using apostrophe just like other ICU
   constructs.
5. Remove dependency on DOMParser and restrictions on void element like
   <link>. This effectively means you don't need to polyfill DOMParser in
   Node anymore

fix(intl-messageformat-parser): fix escaping for XML tag

[email protected]

4.0.0 (2020-03-04)

Features

• intl-messageformat: combine formatHTMLMessage into format (d59fbf1)
• intl-messageformat-parser: Add native support for parsing XML tag (51c49fa)

BREAKING CHANGES

• intl-messageformat: We've modified the way we parse and format embedded
  XML/HTML as follow:

1. formatHTMLMessage has been combined with format
2. All tags specified must have corresponding values and will throw
   error if it's missing, e.g: new IntlMessageFormat("a <b>strong</b>").format({ b: (...chunks) => <strong>chunks</strong> })
3. Self-closing tags are treated as string literal by default. We don't
   allow formatting self-closing tags because we already use ICU
   {placeholder} syntax for that.
4. XML/HTML tags are escaped using apostrophe just like other ICU
   constructs.
5. Remove dependency on DOMParser and restrictions on void element like
   <link>. This effectively means you don't need to polyfill DOMParser in
   Node anymore

fix(intl-messageformat-parser): fix escaping for XML tag

• intl-messageformat-parser: This changes the AST and causes potential conflicts
  with previous parser version
  fix(eslint-plugin-formatjs): Adapt to new parser
  chore(babel-plugin-react-intl): update package lock

[email protected]

2.0.0 (2020-03-04)

Features

• intl-messageformat-parser: Add native support for parsing XML tag (51c49fa)

BREAKING CHANGES

• intl-messageformat-parser: This changes the AST and causes potential conflicts
  with previous parser version
  fix(eslint-plugin-formatjs): Adapt to new parser
  chore(babel-plugin-react-intl): update package lock

[email protected]

6.0.0 (2020-03-04)

Features

• intl-messageformat-parser: Add native support for parsing XML tag (51c49fa)

BREAKING CHANGES

• intl-messageformat-parser: This changes the AST and causes potential conflicts
  with previous parser version
  fix(eslint-plugin-formatjs): Adapt to new parser
  chore(babel-plugin-react-intl): update package lock

@formatjs/[email protected]

1.1.21 (2020-03-04)

Note: Version bump only for package @formatjs/cli

[email protected]

1.6.0 (2020-03-01)

Features

• eslint-plugin-formatjs: add support for defaultMessage (#524) (63742d6)

@formatjs/[email protected]

1.2.1 (2020-03-01)

Bug Fixes

• @formatjs/intl-displaynames: minify locale data JS in dist folder (89a96a3)

@formatjs/[email protected]

1.2.0 (2020-02-02)

Features

• @formatjs/intl-displaynames: include a polyfill-locales.js build that has all locale data (#525) (c260e93)