deprecate @slack/client if it's flagged as legacy?

[jimmywarting]

if @slack/client is marked as legacy, should you deprecate it then?
See how: https://docs.npmjs.com/cli/v8/commands/npm-deprecate

[mwbrooks]

Hey @jimmywarting, that's a great suggestion and I'm a little surprised that we overlooked it! I'm going to loop in a few teammates/maintainers to double-check that there wasn't a reason why we didn't mark the npm package as deprecated.

@stevengill @seratch Do you know if there's a reason why we haven't marked this package as deprecated in package.json?

[seratch]

@mwbrooks I am sure that there is no blocker for marking the package deprecated.

[github-actions]

👋 It looks like this issue has been open for 30 days with no activity. We'll mark this as stale for now, and wait 10 days for an update or for further comment before closing this issue out. If you think this issue needs to be prioritized, please comment to get the thread going again! Maintainers also review issues marked as stale on a regular basis and comment or adjust status if the issue needs to be reprioritized.

[jimmywarting]

still not deprecated...

[hello-ashleyintech]

I have deprecated the @slack/client package and have a PR open to update the package's README to reflect its deprecation. I'll close this issue out once the PR to update the README is added in. 🙌 Thanks again for the awesome suggestion, @jimmywarting!