Pelle Wessman

Version `7.34.4` had this: ```json "peerDependencies": { "eslint": "^3 || ^4 || ^5 || ^6 || ^7 || ^8" }, ``` Version `7.35.0` had this: ```json "peerDependencies": { "eslint": "^3...

I was thinking with a `with-ancestry: true` or something like that

> The second option can be consumed using the `tsconfig.json` by the following way. > > ```json > { > "compilerOptions": { > "types": ["@fastify/static/fastify-global"] > } > } >...

I think this would be a partial revert of #181 from 5 years ago, more specifically of https://github.com/standard/standard-engine/pull/181/commits/d4c291662359d852dc04ecd227aff5a0b76f98c7, which I'm 👍 on, this seems like a needless optimization As @wesleytodd...

@regseb So the user themselves install `standard` rather than it being included by you?

@JoshuaKGoldberg Do we still need this when the new site is ready?

@ifeltsweet @darcyrush The preferable way to do that would be to make a `RequestError` or similar that has a `request` as a property Then you can log it in a...

For historical context: The main reason why Error causes can be any value is because all of `throw`, `Promise.reject()`, the `catch` in a try-catch etc historically can be of any...

An alternative that I looked into some years ago was to align with what Node.js itself does when it serializes: https://github.com/voxpelli/pony-cause/pull/23 Would be kind of nice to fix this "upstream"...

A lock would help, I think I would personally want the option to completely skip bridging such posts as well also, if the quoted post is locked down to Bluesky...