fix: incorrect return type for async produceWithPatches

[mylesj]

👋 Hello, it looks to be a long standing definition but this line seems to be incorrect.

For reference:

[netlify]

✅ Deploy Preview for quizzical-lovelace-dcbd6a canceled.

Name	Link
🔨 Latest commit	c91a842
🔍 Latest deploy log	https://app.netlify.com/sites/quizzical-lovelace-dcbd6a/deploys/62731e76f8a8dd000869e24e

[coveralls]

Pull Request Test Coverage Report for Build 2273093401

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 98.553%

---

Totals
Change from base Build 2257376231:	0.0%
Covered Lines:	786
Relevant Lines:	794

---

💛 - Coveralls

[mweststrate]

Nice catch, thanks!

[github-actions]

🎉 This PR is included in version 9.0.13 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[weihomechen]

Has async produceWithPatches been removed in v10 ？

I can't use like this:

 produceWithPatches({a: 0}, async d => {
        await Promise.resolve()
        d.a = 1
 }).then(([nextState, patches, inversePathes]) => {
 }))

[mylesj]

@weihomechen Looks like a yes,

• Immer 10 proposals: Drop promises, default export, array.length patches, ES5 mode, and make getter / setter support opt-in #1015

Drop promise based producer support. Immer supports returning a promise from a producer. I don't think I ever saw usage of that in the wild, and it is a bit of an oxymoron as it makes it easy to leak drafts. Since producers should be like enter-write-exit without happening anything in the mean time, and it complicates the code base unnecessarily, I'm proposing to simply drop it.

[weihomechen]

@weihomechen Looks like a yes,

• Immer 10 proposals: Drop promises, default export, array.length patches, ES5 mode, and make getter / setter support opt-in #1015

Drop promise based producer support. Immer supports returning a promise from a producer. I don't think I ever saw usage of that in the wild, and it is a bit of an oxymoron as it makes it easy to leak drafts. Since producers should be like enter-write-exit without happening anything in the mean time, and it complicates the code base unnecessarily, I'm proposing to simply drop it.

I have to say it's a bad 'news' ...
but thanks @mylesj anyway