Thomas Hunkapiller

I'm seeing a similar issue here, on node v18.7.0. ```js function log(label) { return (...args) => console.log(`[${label}]`, ...args); } function wait() { return new Promise((resolve) => setImmediate(() => resolve())); }...

Right, so just to make sure I'm clear there, the fix would look like this: ```js function wait() { return new Promise((resolve) => setTimeout(resolve, 0)); } function test() { const...

@BridgeAR okay, but this code has the same problem even though it handles an imaginary `wait` rejection. ```js function wait() { return new Promise((resolve) => setTimeout(resolve, 0)); } function test()...

I'm seeing even worse behavior with the async/await syntax. What is even going on here? ``` [devoidfury@oryx errors]$ cat demo.js function wait() { return new Promise((resolve) => setTimeout(resolve, 0)); }...

The problem I have with this is, unlike most other scenarios where an error pops up, is there's nothing in that stack trace you can search on the internet to...

Yes, that's exactly right, just adding some important keywords to the stack trace to make it more informative, discoverable, searchable, learnable; having the location the problem occurred is great, but...

Is it a specific timezone that's incorrect? It also lists the GMT offset, does that match your expectations? I tried it for my timezone (chicago) and it was correct.

It was a lot of fun. Thanks @vartan ! (sorry I bailed the last couple days, crunch time and a product launch)

It is in there, are you on version 7.x? https://github.com/dolanmiu/docx/blob/75d62723b68f557e60fef9cc09e47bdeed0b76cb/src/file/file.ts#L56 https://github.com/dolanmiu/docx/blob/75d62723b68f557e60fef9cc09e47bdeed0b76cb/src/file/core-properties/properties.ts#L30-L33

Can you add any more details? A code sample that demonstrates the issue?