Tetsuharu Ohzeki

Add the step to check subscriber's active state to next(value)/error(error)/complete() as a shortcut

6

Fix https://github.com/WICG/observable/issues/114 *** Preview | Diff

Should add the checking subscriber's `active` state to the first step of `next(value)`/`error(error)`/`complete()` methods?

3

These supporting concepts does not check _subscriber_'s [_active_](https://wicg.github.io/observable/#subscriber-active) state. - https://wicg.github.io/observable/#dom-subscriber-next - https://wicg.github.io/observable/#dom-subscriber-error - https://wicg.github.io/observable/#dom-subscriber-complete And they use as null checking for each of _next/error/complete algorithm_ instead of checking _active_...

feat: Support mode flag by `verbatimSymlinks` polyfill

1

### Is there an existing issue for this? - [X] I have searched the existing issues ### Current Behavior Node.js v17.6.0 (also v16.15.0) add the support `verbatimSymlinks` option to [fsPromises.cp()](https://nodejs.org/docs/latest-v20.x/api/fs.html#fspromisescpsrc-dest-options)....

feat: Support `mode` flag by `cp()` polyfill

1

### Is there an existing issue for this? - [X] I have searched the existing issues ### Current Behavior Node.js v20.1.0 add the support `mode` flag to [`fsPromises.cp()`](https://nodejs.org/docs/latest-v20.x/api/fs.html#fspromisescpsrc-dest-options). But the...

Reconsider object shape for PlainResult

2

[The current object shape of `PlainResult`](https://github.com/option-t/option-t/blob/e6fdbd184df5c4ff12def0753fb565660c205d1e/packages/option-t/src/plain_result/result.ts) was designed to have some compatibility with `PlainOption`. But its attempts was not success and it's just backward compat. `PlainOption` is now deprecated. So...

Drop Node.js v20 from CI

1

Fix https://github.com/option-t/option-t/issues/2384

https://github.com/option-t/option-t/issues/2244