Add symbol/replace and has-replace-symbol-support packages

[aryan7071]

Resolves #8479

Description

This pull request implements the RFC to add support for two new packages:

1. @stdlib/symbol/replace

• Exports Symbol.replace when supported by the environment.
• Exports undefined in environments without native Symbol.replace support.
• Includes documentation, examples, benchmarks, TypeScript types, and tests.
• Mirrors the structure and conventions used by existing symbol-related packages such as:
  • symbol/iterator
  • symbol/async-iterator
  • symbol/has-instance

2. @stdlib/assert/has-replace-symbol-support

• Provides feature detection for native Symbol.replace.
• Exports a boolean indicating support.
• Includes:
  • Library implementation
  • Test suite
  • Benchmarks
  • CLI (has-replace-symbol-support)
  • Examples
  • TypeScript definitions and TS tests
  • README and usage docs

This PR follows the package-creation checklist outlined in the RFC:

• Copied from a similar existing package
• Renamed package and variable names
• Updated copyright years to 2025
• Updated documentation and examples to reflect Symbol.replace
• Verified the implementation through local testing

---

Related Issues

• [RFC]: add symbol/replace — [RFC]: add symbol/replace #8479

---

Questions

No.

---

Other

No additional information.

---

Checklist

• Read, understood, and followed the contributing guidelines.

AI Assistance

When authoring the changes proposed in this PR, did you use any kind of AI assistance?

• Yes
• No

If you answered "yes" above, how did you use AI assistance?

• Code generation (e.g., when writing an implementation or fixing a bug)
• Test/benchmark generation
• Documentation (including examples)
• Research and understanding

Disclosure

This PR was authored and implemented by me. I used ChatGPT to help with formatting, code and test scaffolding, documentation consistency, and to confirm that the package layout and conventions match other stdlib packages. All final code, edits, and decisions were reviewed and approved by me before submission.

---

@stdlib-js/reviewers

[stdlib-bot]

👋 Hi there! 👋

And thank you for opening your first pull request! We will review it shortly. 🏃 💨

Getting Started

• Please read our contributing guidelines if you haven't already.
• For development guidance, refer to the development guide.

Next Steps

1. A project maintainer will approve GitHub Actions workflows for your PR.
2. All CI checks must pass before your submission can be fully reviewed.
3. You'll need to address any failures in linting or unit tests.

Running Tests Locally

You can use make to run any of the CI commands locally from the root directory of the stdlib repository:

# Run tests for all packages in the math namespace:
make test TESTS_FILTER=".*/@stdlib/math/.*"

# Run benchmarks for a specific package:
make benchmark BENCHMARKS_FILTER=".*/@stdlib/math/base/special/sin/.*"

If you haven't heard back from us within two weeks, please ping us by tagging the "reviewers" team in a comment on this PR.

If you have any further questions while waiting for a response, please join our Gitter channel to chat with project maintainers and other community members.

We appreciate your contribution!

Documentation Links

• Contributing Guidelines
• Development Guide
• Gitter channel
• make rules for running examples
• make rules for running unit tests
• make rules for running benchmarks

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
assert/has-replace-symbol-support	$\color{green}91/91$ $color{green}+100.00%$	$\color{green}6/6$ $color{green}+100.00%$	$\color{green}1/1$ $color{green}+100.00%$	$\color{green}91/91$ $color{green}+100.00%$
symbol/replace	$\color{green}90/90$ $color{green}+100.00%$	$\color{red}2/3$ $color{green}+66.67%$	$\color{green}0/0$ $color{green}+100.00%$	$\color{green}90/90$ $color{green}+100.00%$

The above coverage report was generated for the changes in this PR.

[kgryte]

@aryan7071 I suggest learning how to better prompt and leverage AI, as many of the changes to the existing package are undesired. As a first time contributor, I suggest spending time authoring contributions manually before using AI, as it is critical to familiarize yourself with project conventions in order to know expectations and standards.

[aryan7071]

Thanks for the feedback. @kgryte sir
As a first-time contributor, I did rely too heavily on AI to speed things up, and I understand that some of the changes didn’t fully align with the project’s conventions.
I’ll take your advice and spend more time understanding the codebase, guidelines, and standards. Going forward, I’ll author contributions manually first and use AI only as a helper where appropriate not as a substitute for my own understanding.
Thanks again for the guidance. I genuinely want to improve and contribute in the right way.

[kgryte]

Ref: a68d5d9

[stdlib-bot]

Thank you for working on this pull request. However, we cannot accept your contribution as the issue this pull request seeks to resolve has already been addressed in a different pull request or commit.

Thank you again for your interest in stdlib, and we look forward to reviewing your future contributions.