chore: fix JavaScript lint errors (issue #10501)

[aryan7071]

---

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: passed
• 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 ---

Resolves #10501

Description

What is the purpose of this pull request?

This pull request:

• Resolves Fix JavaScript lint errors #10501

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• #{{TODO: add related issue number}}

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

• 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

If you answered "yes" to using AI assistance, please provide a short disclosure indicating how you used AI assistance. This helps reviewers determine how much scrutiny to apply when reviewing your contribution. Example disclosures: "This PR was written primarily by Claude Code." or "I consulted ChatGPT to understand the codebase, but the proposed changes were fully authored manually by myself.".

{{TODO: add disclosure if applicable}}

---

@stdlib-js/reviewers

[stdlib-bot]

Hello! 👋

We've noticed that you've been opening a number of PRs addressing good first issues. Thank you for your interest and enthusiasm!

Now that you've made a few contributions, we suggest no longer working on good first issues. Instead, we encourage you to prioritize cleaning up any PRs which have yet to be merged and then proceed to work on more involved tasks.

Not only does this ensure that other new contributors can work on things and get ramped up on all things stdlib, it also ensures that you can spend your time on more challenging problems. 🚀

For ideas for future PRs, feel free to search the codebase for TODOs and FIXMEs and be sure to check out other open issues on the issue tracker. Cheers!

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
bigint/ctor	$\color{green}70/70$ $\color{green}+100.00%$	$\color{red}2/3$ $\color{green}+66.67%$	$\color{green}0/0$ $\color{green}+100.00%$	$\color{green}70/70$ $\color{green}+100.00%$
utils/memoize	$\color{green}162/162$ $\color{green}+100.00%$	$\color{green}13/13$ $\color{green}+100.00%$	$\color{green}2/2$ $\color{green}+100.00%$	$\color{green}162/162$ $\color{green}+100.00%$

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

[Planeshifter]

Thanks for opening a PR!

[Planeshifter]

The lint rule stdlib/no-builtin-big-int has an allowance for BigInt when imported via require( '@stdlib/bigint/ctor' ) (see the isImportedBigInt check). The rule only fires here because the example uses a relative path ./../lib instead of the full package path. We should disable it:

Suggested change

	var bigint = require( './../lib' );
	var BigInt = require( '@stdlib/bigint/ctor' ); // eslint-disable-line stdlib/no-builtin-big-int

[Planeshifter]

Should stay as BigInt( '1' ):

Suggested change

	v = bigint( '1' );
	v = BigInt( '1' );

[aryan7071]

Hi @Planeshifter,

After applying your suggested changes, the CI is throwing two errors:

22:14  error  Last `require` statement in example files must be a relative path  stdlib/require-last-path-relative
22:48  error  Unused eslint-disable directive (no problems were reported from 'stdlib/no-builtin-big-int')

It seems like using require( '@stdlib/bigint/ctor' ) with // eslint-disable-line stdlib/no-builtin-big-int satisfies the no-builtin-big-int rule (making the disable directive unused/unnecessary), but then fails require-last-path-relative since it's not a relative path.

could you please guide me on this ? thank you !