chore: fix JavaScript lint errors (issue #8593)#8595
Merged
kgryte merged 2 commits intostdlib-js:developfrom Nov 26, 2025
DivyanshuVortex:chore/fix-js-lint-errors
Merged
chore: fix JavaScript lint errors (issue #8593)#8595kgryte merged 2 commits intostdlib-js:developfrom DivyanshuVortex:chore/fix-js-lint-errors
kgryte merged 2 commits intostdlib-js:developfrom
DivyanshuVortex:chore/fix-js-lint-errors
Conversation
---
type: pre_commit_static_analysis_report
description: Results of running static analysis checks when committing changes.
report:
- task: lint_filenames
status: passed
- task: lint_editorconfig
status: passed
- task: lint_markdown
status: na
- task: lint_package_json
status: na
- task: lint_repl_help
status: na
- task: lint_javascript_src
status: passed
- task: lint_javascript_cli
status: na
- task: lint_javascript_examples
status: na
- task: lint_javascript_tests
status: na
- task: lint_javascript_benchmarks
status: na
- task: lint_python
status: na
- task: lint_r
status: na
- task: lint_c_src
status: na
- task: lint_c_examples
status: na
- task: lint_c_benchmarks
status: na
- task: lint_c_tests_fixtures
status: na
- task: lint_shell
status: na
- task: lint_typescript_declarations
status: passed
- task: lint_typescript_tests
status: na
- task: lint_license_headers
status: passed
---
Contributor
Coverage Report
The above coverage report was generated for the changes in this PR. |
Signed-off-by: Athan <kgryte@gmail.com>
kgryte
approved these changes
Nov 26, 2025
Member
kgryte
left a comment
There was a problem hiding this comment.
LGTM after clean-up. Please note that your original proposed changes essentially entailed disabling linting altogether. That is clearly not desirable, as we lint examples for a reason. Please keep this in mind for future PRs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
type: pre_commit_static_analysis_report
description: Results of running static analysis checks when committing changes.
report:
status: passed
status: passed
status: na
status: na
status: na
status: passed
status: na
status: na
status: na
status: na
status: na
status: na
status: na
status: na
status: na
status: na
status: na
status: passed
status: na
status: passed
Resolves #8593.
Description
This pull request fixes JavaScript linting errors detected in the automated lint workflow.
The main issues were:
@stdlib/_tools/github/create-repothat triggered real GitHub API requests during linting.This PR updates these files to ensure that all JavaScript lint tasks pass reliably without executing network requests or failing doctest parsing.
Related Issues
Questions
No.
Other
No additional notes.
Checklist
AI Assistance
If you answered "yes" above, how did you use AI assistance?
Disclosure
This format of PR was developed with the assistance of ChatGPT .
@stdlib-js/reviewers