v3.2.2 not support SSR

[ycjcl868]

relate commit ace1a9d.

In node env, there's no Intl.RelativeTimeFormat, so it will throw Error.

In my opinion, it's a breaking change, it shouldn't block the main process in Server-Side render

[longlho]

Yes you should polyfill Intl.RelativeTimeFormat in Node

…

On Wed, Sep 18, 2019 at 6:59 AM 信鑫-King ***@***.***> wrote: [image: image] <https://user-images.githubusercontent.com/13595509/65142940-5deeae80-da46-11e9-8797-a89088c0d78a.png> in node env, there's no Intl.RelativeTimeFormat, so it will throw Error. [image: image] <https://user-images.githubusercontent.com/13595509/65142968-71017e80-da46-11e9-89d2-fde4298fc61b.png> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1487>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABQM3ZYWOQG4NWF2KVVHW3QKICZXANCNFSM4IX5C4HQ> .

[zombieJ]

@longlho,
Do not bring breaking change in patch version. This should move to minor version or use console warning in patch version instead.

[longlho]

Actually that was a mistake on our part. It has always required Intl.RelativeTimeFormat, just lazily. Publishing a fix now.

[longlho]

fixed in 3.2.3. Thanks for reporting!