Trevor Vaughan

I also did a little tinkering and I think the biggest issue is if you want to make the paging "easy". For instance, you'd have to process the statement to...

🤔 Actually, looking at the original post query, you can end up with a bunch of endpoints with paging. Well, you could possibly make people add the paging hooks if...

Just had a case where `curl` works but `@gitbeaker` doesn't. This would definitely be super helpful!

It didn't. I'm having issues with the `ProtectedBranches.edit` function kicking back a `400 Bad Request`. I patched in the branch and inspected the request and it honestly looks fine from...

I'll see what I can do. I'm going to try rolling back a few versions and see if it works (it certainly used to).

Looks like the last time it worked was back in `@gitbeaker/node` 35.8.0

I tried passing everything into the raw `requester` with the same result. 🤔 Could it be related to `patch`? The other functions on that endpoint work just fine.

I hacked around it using straight `got.patch` and that worked but :-(. 🤔 I recently moved off of `node-fetch` for 16 => 18 compat. I'll try using `node-fetch` again.

🤦 Welp, @marcelstoer You hit the nail on the head. Overriding the inbuilt `fetch` with `node-fetch` worked. 💀

For anyone else that hits this, here's a horrible hack-around for the entry-point to your app: ```javascript const semver = require('semver') if ( semver.lt(process.version, '20.0.0') ) { global.fetch = require('node-fetch')...