Open kaiyoma opened 2 years ago
Thanks for reporting this issue.
Yes, this project is still active, and it's widely used in many Alibaba production system. So don't worry.
For the issues mentioned above, are still fixing in progress. However, most of the them are caused from dependency packages which have break changes. I already filed some issues to them to ask if they could provide a way to keep compatible. This may takes some time.
Recently, I did an overhaul of i18n in my org's large enterprise product. We were using
react-intl-universal
and I was happy to keep using it, but we ran into a number of problems and ended up switching to another library out of frustration. All of the issues that I found could have easily been avoided with a minimal amount of continual maintenance. I'm offering some feedback on my experience in the hopes that maybe it'll help this project move forward.console-polyfill
errors in one of the tools in our org. When I tracked down why we even had that dependency, I found that it was coming fromreact-intl-universal
. I have no idea why this library even needs to exist, sinceconsole
is present in both the browser and Node. I filed a bug (https://github.com/alibaba/react-intl-universal/issues/182) and to the credit of the maintainers, the offending dependency was removed immediately.npm i
and it finally worked, so it would appear something is wrong with the current lockfile.npm i
finally worked, it printed out a lot of deprecation warnings. This project is not staying up to date with the rest of npm. You should consider a Renovate bot (https://github.com/renovatebot/renovate) or something similar.All in all, my experience with poking around the project was not good and convinced me to migrate to a library that's better maintained. I hope this feedback helps you make your project better for others.