Skip to content
This repository has been archived by the owner on May 4, 2020. It is now read-only.

Commit

Permalink
Publish
Browse files Browse the repository at this point in the history
  • Loading branch information
longlho committed May 17, 2019
1 parent 8c4c894 commit 4c70d84
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion packages/formatjs-extract-cldr-data/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "formatjs-extract-cldr-data",
"version": "6.0.0",
"version": "6.1.0",
"description": "Utility library that extracts the CLDR data that's needed by the FormatJS libraries.",
"main": "index.js",
"scripts": {
Expand Down
2 changes: 1 addition & 1 deletion packages/intl-messageformat-parser/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "intl-messageformat-parser",
"version": "1.5.1",
"version": "1.6.0",
"description": "Parses ICU Message strings into an AST via JavaScript.",
"main": "index.js",
"jsnext:main": "src/parser.js",
Expand Down

3 comments on commit 4c70d84

@macca16
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe the upgrade to 1.6.0 caused issues with usage in browser due to missing default export on intl-messageformat-parser when used from intl-messageformat

I was able to fix this by removing the line "browser": "lib/parser.js", from package.json - which resulted in index.js adding the default to the /lib/parser.js version

@longlho
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

intl-messageformat dependency on intl-messageformat-parser is still hardcoded at 1.4.0 but thanks a lot for raising this. Do you mind creating a Github issue so we can track this?

@macca16
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I see that, although babel-plugin-react-intl is not pegged to 1.4.0 so for me at least this breaks. Have forced downgrade for now, will add an issue

Please sign in to comment.