Hyeon Dokko

@ixartz ok, so I prepared to pr, but wanna get your advice. 1. bugs in npm v8 check this link: https://github.com/storybookjs/storybook/issues/18298 I'm using node v18 and npm v8. I try...

@ixartz Thank you for advice! 1. I haven't seen ```legacy-peer-deps``` cause problems when project hasn't storybook. I'll check to see if there's a way to apply it only to storybook....

@ixartz Cool:)

@ixartz well.. npm v19 also make problem. So I'm finding how can use ```legacy-peer-deps``` only storybook:) 

@ixartz It just occurred to me that legacy-peer-deps ignores peer dependency conflicts. As of now, both dev and prod seem to be working in local without any problems. But what...

> > [Jotai](https://jotai.org/) means a state in Japanese. I guess you have already known this. From the same perspective, The name `Sangte` looks okay. > > @kyun > > Agreed,...

@markerikson We should look at the definition of isSuccess in the values in '**initialized**' state. `const isSuccess = currentState.isSuccess || isFetching && hasData;` If the state is '**initialized**', isFetching(_isLoading_) is...

@riqts > The flashing of the `isSuccees` is almost certainly unintended. I have experienced the flashing of a feature that corresponds to `isSuccess` in other famous query libraries in my...

Hi @JLHwung I’ve reproduced and fixed the case where, after a private key, the trailing destructuring segment could read named properties from an already excluded object (making x become undefined)....