Skip to content

date.toString timezone differences in v10.4.x #21390

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ravishivt opened this issue Jun 18, 2018 · 1 comment
Closed

date.toString timezone differences in v10.4.x #21390

ravishivt opened this issue Jun 18, 2018 · 1 comment
Labels
v8 engine Issues and PRs related to the V8 dependency.

Comments

@ravishivt
Copy link

  • Version: v10.4.1
  • Platform: Linux 8a47e98f5019 4.9.87-linuxkit-aufs deps: update openssl to 1.0.1j #1 SMP Wed Mar 14 15:12:16 UTC 2018 x86_64 Linux (docker node:10.4.1-alpine container)
  • Subsystem: unknown

v10.4.0 does not abbreviate the timezone. I think this is due to the V8 6.6 -> 6.7 upgrade in #19989 as per this comment but wanted to confirm this is the correct behavior. The change has affected many of my jest snapshots.

v10.3.0:

# node -e 'console.log((new Date(0)).toString())'
Thu Jan 01 1970 00:00:00 GMT+0000 (UTC)

v10.4.1 (and v10.4.0):

# node -e 'console.log((new Date(0)).toString())'
Thu Jan 01 1970 00:00:00 GMT+0000 (Coordinated Universal Time)
@ravishivt
Copy link
Author

I found https://bugs.chromium.org/p/v8/issues/detail?id=6076#c10 which indicates V8 did make this change on purpose. Closing this since this is now expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v8 engine Issues and PRs related to the V8 dependency.
Projects
None yet
Development

No branches or pull requests

2 participants