fix(docs): remove broken @std/log link from README

[jeremylongshore]

Summary

The jsr.io/@std/log URL in the README returns 404. This PR removes the broken link while preserving all other working logger examples (pino, winston, bunyan, consola, signale).

Test plan

• Verified jsr.io/@std/log returns 404
• Verified all other logger links return 200

🤖 Generated with Claude Code

[felixfbecker]

The link works for me? https://jsr.io/@std/log

[jeremylongshore]

Hi @felixfbecker! Thanks for reviewing.

I just re-checked and https://jsr.io/@std/log still returns 404 for me:

$ curl -sI "https://jsr.io/@std/log" | head -3
HTTP/2 404 
content-type: text/plain

The package might have been moved or renamed. The correct URL appears to be https://jsr.io/@std/log/doc (with /doc suffix) or it may have been consolidated into @std/.

Would you like me to:

1. Update to use the correct URL if you know what it should be?
2. Keep the removal since the documented link doesn't work?

Happy to adjust based on your preference!

[0xrdan]

A more compelling reason to remove or adjust it can be found in the package's issue #6124 thread, which is linked in the url's page at "@std/log is likely to be removed in the future. Consider using Open Telemetry."

[felixfbecker]

It appears that it returns a different HTTP response when you use curl vs if you access the link in the browser

[felixfbecker]

@dtmeadows wdyt about @std/log in general considering the point on deprecation?

[RobertCraigie]

Some people are still relying on it denoland/std#6124 (comment), what's the benefit in removing the link?

[jeremylongshore]

Thank you for the feedback, @RobertCraigie. You raise a fair point - if people are still relying on it and the link works in browser, there's no strong reason to remove it.

I'm happy to close this PR. Appreciate you and @felixfbecker taking the time to review.

[jeremylongshore]

Actually, to clarify - the link does return a 404 when accessed programmatically:

curl -sI "https://jsr.io/@std/log" | head -1
HTTP/2 404

It only works in browser due to JavaScript. So documentation links that require JS to resolve aren't ideal.

Combined with @0xrdan's point that @std/log is likely to be removed per denoland/std#6124, there may still be value in updating this.

That said, I understand if you'd prefer to keep it as-is. Happy either way - just wanted to clarify the original reasoning. Thank you again for reviewing.