3 ms·
This has nothing to do with multithreading, though?
by christophilus 1y ago
This has nothing to do with multithreading, though?
- cookiengineer 1y agoNot OP but wasn't the article about lots of async/await context issues? If the handle() method of the middleware API would have provided, say, a context.Context parameter, most of the described debugging issues would have been gone, no?
- h4ck_th3_pl4n3t 1y agoYes, that's what I meant
- arnorhs 1y agoAbsolutely correct. Those are runtime execution context-issues. There are other frameworks that do force you do deal with those (and in other languages, probably), but I believe in next.js the difficulies are at another level - because of poor documentation and the built in abstractions to allow for running next.js both in development, node.js server, and edge.