Dmitry Zakharov
Dmitry Zakharov
I don't know what's the problem, but if we ignore the problem the sorting at least works. Also, I've checked, the object inside of the list isn't frozen nor with...
Ah, no, I'm wrong. It's both Frozen and sealed. For this line ```js console.log(newList, newList[evt.oldIndex], evt, Object.isFrozen(newList[evt.oldIndex]), Object.isSealed(newList[evt.oldIndex]), Object.isExtensible(newList[evt.oldIndex])); ``` It returned the following thing:  I'm gonna create a...
@prtk0317, well, immer weights 1kb more than this library. Moreover, there is absolutely no need in this useless abstraction.
How about to close the issue?
@sanchito59 My problem was because of immer, that made objects frozen. UseMemo shouldn't affect values in any way. If it does, you can try the last commit from the master...
It's fixed after formatting the file on save.
I'll try the feature for longer time and give more feedback.
> For the sake of semantics, I'd rather have res:watch than res:dev, since the latter would look similar to npm run dev which is very common in e.g. a NextJS...
Am I right that by "completed" it means completely closed?
Simple answer is: ```js export const migrations = { 16: () => ({}), }; ```