Temporal behavior is not spec-compliant

Version

26.0.0

Platform

Darwin (redacted host name) 25.4.0 Darwin Kernel Version 25.4.0: Thu Mar 19 19:32:36 PDT 2026; root:xnu-12377.101.15~1/RELEASE_ARM64_T8103 arm64

Subsystem

No response

What steps will reproduce the bug?

bugs for iso8601 calendar which are already fixed in upstream:

// 1.
new Temporal.Duration(0, 1, 0, 0, 1).round({ smallestUnit: 'months', roundingMode: 'expand', relativeTo: new Temporal.PlainDate(2020, 1, 31) }).toString();
// 2.
Temporal.Instant.from('2020-01-01T00:00:00.1234567890Z');

incorrect behavior for non-ISO calendars:

// 3.
Temporal.PlainDate.from({ year: 2020, month: 1, day: 40, calendar: 'gregory' });
// 4.
Temporal.PlainDate.from({ year: -1, month: 1, day: 1, calendar: 'gregory' });
// 5.
Temporal.PlainDate.from({ year: 5786, monthCode: 'M05L', day: 1, calendar: 'hebrew' });
// 6.
Temporal.PlainDate.from('2026-05-01[u-ca=chinese]').year;

How often does it reproduce? Is there a required condition?

always, without any conditions

What is the expected behavior? Why is that the expected behavior?

"P2M"
RangeError is thrown
RangeError is not thrown
RangeError is not thrown
RangeError is not thrown
2026

What do you see instead?

"PT0S"
RangeError is not thrown
RangeError is thrown
RangeError is thrown
RangeError is thrown
4663

Additional information

I tested Temporal test cases in test262, and Node.js failed for many cases, mainly due to wrong behavior for non-ISO calendars. I suspect this is because Node.js uses outdated temporal_rs and ICU4X (but I haven't confirmed my guess yet).

@legendecas

We never did land a cargo updater after #61151. (cc @legendecas)

A newer version of temporal_rs update needs V8 to be updated as well.

node/deps/v8/DEPS

Lines 488 to 489 in 267989b

    
           'third_party/rust': 
        
             Var('chromium_url') + '/chromium/src/third_party/rust' + '@' + '30eb036e9b2f181dda31bde6f20d2a4983e380b9',

https://chromium.googlesource.com/chromium/src/third_party/rust/+/30eb036e9b2f181dda31bde6f20d2a4983e380b9/temporal_rs/v0_1/README.chromium shows version 0.1.2, while we're on version 0.1.0:

node/deps/crates/Cargo.lock

Lines 339 to 341 in 267989b

    
           [[package]] 
        
           name = "temporal_rs" 
        
           version = "0.1.0"

#63281 solves cases 3-6. Cases 1 and 2 weren't addressed until temporal_rs 0.2.0.

chore(deps): bump temporal-polyfill and temporal-spec to 1.0.0

deps: update Rust crates for V8 14.6.202.34-node.26

Navigation Menu

Repository navigation

`Temporal` behavior is not spec-compliant #63145

Version

Platform

Subsystem

What steps will reproduce the bug?

How often does it reproduce? Is there a required condition?

What is the expected behavior? Why is that the expected behavior?

What do you see instead?

Additional information

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

	'third_party/rust':
	Var('chromium_url') + '/chromium/src/third_party/rust' + '@' + '30eb036e9b2f181dda31bde6f20d2a4983e380b9',

Temporal behavior is not spec-compliant #63145

Description

Version

Platform

Subsystem

What steps will reproduce the bug?

How often does it reproduce? Is there a required condition?

What is the expected behavior? Why is that the expected behavior?

What do you see instead?

Additional information

Activity

Renegade334 commented on May 6, 2026

legendecas commented on May 8, 2026

aduh95 commented on May 13, 2026

Renegade334 commented on May 13, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

`Temporal` behavior is not spec-compliant #63145