getting utc in wasm

[jaroslaw-weber]

Is there a workaround for making chrono work with wasm? I want to get current time (utc). I am using wasm-unknown-unknow flag.

[quodlibetor]

What is the error that you're running into? I haven't done any work with it, but running with no-default-features might help you out.

[ablwr]

I'm having this problem as well, and this user reporting in the time repo gets the same errors as I do: time-rs/time#163

[CryZe]

I'd like to see some wasm support as well. While disabling the local feature should work, it doesn't work for crates that have to work on other targets as well, due to cargo not being able to selectively enable / disable features for certain targets. So it would be cool if chrono either had specific wasm support (by using Web APIs or defining its own external interface) or just automatically cfging out the local feature when targeting wasm. If not, I might have to fork chrono :(

[CryZe]

Would it be if I would just send a PR real quick that extends all the local cfgs to also check for wasm? That'd be a fast and easy, but slightly dirty fix (although somewhat necessary for the meantime).

[quodlibetor]

@CryZe yes I'd be curious what that looks like, if it's backwards-compatible I'd be happy with it.

[CryZe]

Actually, that wouldn't work, as the time crate would still be pulled in then. Urgh, I guess someone needs to fix cargo then.

[quodlibetor]

If you disable default features we should not be pulling in the time crate.

[jjpe]

Is there a workaround for making chrono work with wasm? I want to get current time (utc). I am using wasm-unknown-unknow flag.

I have a PR waiting to be merged that enables Utc::now() and Local::now to work on WASM.

[David-OConnor]

Still broken

[quodlibetor]

This is fixed.