chore: add missing devDependencies field

[Om-A-osc]

---

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: passed
• task: lint_repl_help
  status: na
• task: lint_javascript_src
  status: na
• 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

---

Description

While investigating a separate issue, I ran make lint-pkg-json and found that the lint_package_json check was failing for one of the packages.

The failure was caused by a missing devDependencies field in package.json. According to the package.json schema enforced by the linting pipeline, devDependencies is a required field. As a result, the Ajv schema validator was flagging this omission as an error.

This pull request fixes the issue by adding the appropriate devDependencies field, bringing the package metadata back into compliance with the schema and allowing the lint step to pass.

Related Issues

None.

Questions

No.

Other

No.

Checklist

• Read, understood, and followed the contributing guidelines.

AI Assistance

• Yes
• No

@stdlib-js/reviewers

[Om-A-osc]

Hi @kgryte and @Planeshifter, please review and merge when convenient. All package-json lints are passing now.
Thanks!

[Planeshifter]

Thanks!

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	remark-html@​10.0.0
	read-installed@​4.0.3
	mathjax-node-sre@​3.0.3
	remark-vdom@​8.0.0
	remark-lint-no-trailing-spaces@​3.0.2
	proxyquire-universal@​2.1.0
	process@​0.11.10
	proxyquire@​2.1.3
	lunr@​2.3.9
	virtual-dom@​2.1.1
	tap-xunit@​2.4.1
	vdom-to-html@​2.3.1
	mathjax-node@​2.1.1
	plato@​1.7.0
	proxyquireify@​3.2.1
	tap-spec@​5.0.0
	uglifyify@​5.0.2
	tap-summary@​4.0.0
	parse-link-header@​1.0.1
	remark-lint-no-auto-link-without-protocol@​1.0.4
	remark-lint-no-inline-padding@​1.0.5
	remark-slug@​5.1.2
	to-vfile@​6.1.0
	remark-unlink@​2.1.2
	mkdirp@​0.5.6
	jsdoc@​3.6.11
	resolve@​1.22.11
	remark-lint-linebreak-style@​1.0.4
	remark-lint-no-html@​1.0.4
	remark-lint-no-paragraph-content-indent@​1.0.7
	remark-lint-no-heading-like-paragraph@​1.0.4
	remark-lint-no-reference-like-url@​1.0.5
	remark-lint-no-duplicate-headings-in-section@​1.0.5
	unist-util-visit-parents@​3.1.1
See 74 more rows in the dashboard

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Critical CVE: Unsafe defaults in npm remark-html`` CVE: GHSA-9q5w-79cv-947m Unsafe defaults in remark-html (CRITICAL) Affected versions: = 14.0.0; < 13.0.2; >= 14.0.0 < 14.0.1 Patched version: 13.0.2 From: package.json → npm/remark-html@10.0.0 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/remark-html@10.0.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[stdlib-bot]

PR Commit Message

chore: add missing `devDependencies` field

PR-URL: https://github.com/stdlib-js/stdlib/pull/9840

Co-authored-by: Philipp Burckhardt <pburckhardt@outlook.com>
Reviewed-by: Philipp Burckhardt <pburckhardt@outlook.com>
Signed-off-by: Philipp Burckhardt <pburckhardt@outlook.com>

Please review the above commit message and make any necessary adjustments.