Sʜɪᴍᴜʀᴀ Yū

I think the correct way to achieve this will be: ```ts const values = ['Unknown', 'Online', 'Offline'] as const const Values = Union(...values.map(Literal)) ``` But this is not possible for...

I've tested on current `master` with #166 merged, and noticed it won't work out of the box. We still need some ugly workaround like following: ```ts const values = ['Unknown',...

That should be, definitely. Actually we don't have enough resource to gather accurate info for old versions, but the version number of `typescript` in `package.json` can be a guide for...

Hm, I was just unsure if we should still stick to ES5. If so, it feels like we need to integrate Babel transpilation into our build process, because it's hard...

I see. Personally I don't really have much opposition to maintain ES5 support with Babel in this package's side, but I'm afraid of introducing some performance drop and/or being hit...

Just investigating how we could achieve optimal results, I found https://github.com/developit/microbundle is a good way to go. Integrating a bundler will also result in single file build (for each target),...

This seems to be a feature request rather than a question. If you provide some example code then I can provide a workaround for you. Maybe `.extend()` should work for...

Okay, then you can use `Optional(A).underlying` to unwrap it for now, but it should be deprecated and replaced soon by `.required()` which has more understandable name.

Thanks for sending the bug report, your repro is very helpful. I think there might hardly be any way around this though, I'm going to tinker around the static typing...

Hmm, I think I found a way. Changing the relevant code not to using `Exclude` may resolve the issue, at least in the case of the provided repro. ```ts type...