Update main.js

[VeerRaj-007]

Issue: Using new Array() violates the stdlib/no-new-array rule.

Resolves #{{TODO: add issue number}}.

Description

What is the purpose of this pull request?

This pull request:

• {{TODO: add description describing what this pull request does}}

Related Issues

Does this pull request have any related issues?

This pull request:

• resolves #{{TODO: add 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.

---

@stdlib-js/reviewers

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
utils/async/if-then	$199/199$ $+100.00\mathrm{\%}$	$21/21$ $+100.00\mathrm{\%}$	$3/3$ $+100.00\mathrm{\%}$	$199/199$ $+100.00\mathrm{\%}$

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

[kgryte]

We don't use const.

[VeerRaj-007]

Hi @kgryte ,

Thank you for the feedback. I understand that "const" isn't typically used in this context. I'll adjust my code accordingly to align with the project's coding conventions.

Could you please clarify if there are specific patterns or alternatives you recommend for variable declarations in this situation?

[kgryte]

You can start by actually looking at the file that you are editing.

[kgryte]

@VeerRaj-007 What issue are you trying to resolve?

[VeerRaj-007]

I'm currently working on resolving stdlib/no-new-array linting rule violation in lib/node_modules/@stdlib/utils/async/if-then/lib/main.js (Line 122) which involves The original code uses new Array(nargs), which is flagged by ESLint.

Please let me know if there are specific details you'd like me to provide or if there's anything else I should consider.