Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexpected dependencies in package.json #2469

Closed
2 tasks done
hfhchan-plb opened this issue Jun 28, 2024 · 3 comments
Closed
2 tasks done

Unexpected dependencies in package.json #2469

hfhchan-plb opened this issue Jun 28, 2024 · 3 comments
Labels
Obsolete Issue or pull request which is no longer relevant.

Comments

@hfhchan-plb
Copy link

Description

In all the @stdlib/assert-is-* packages, @stdlib/cli-ctor and @stdlib-fs-read-file are listed as dependencies, when they should be devDependencies.

This causes huge deps trees when importing something simple like @stdlib/math-base-special-ldexp.

Related Issues

No response

Questions

No response

Demo

No response

Reproduction

No response

Expected Results

No response

Actual Results

No response

Version

No response

Environments

N/A

Browser Version

No response

Node.js / npm Version

No response

Platform

No response

Checklist

  • Read and understood the Code of Conduct.
  • Searched for existing issues and pull requests.
@stdlib-bot
Copy link
Contributor

👋 Hi there! 👋

And thank you for opening your first issue! We will get back to you shortly. 🏃 💨

@kgryte
Copy link
Member

kgryte commented Jun 28, 2024

@hfhchan-plb It seems you are using outdated versions of stdlib packages. In the referenced issue (SukkaW/nolyfill#79), the version for @stdlib/assert-is-boolean is v0.0.8. The most recent version is v0.2.1. That, in turn, depends on @stdlib/assert-has-tostringtag-support which no longer directly depends on @stdlib/cli-ctor. See https://www.npmjs.com/package/@stdlib/assert-has-tostringtag-support?activeTab=dependencies and compare with the dependency tree you show in SukkaW/nolyfill#79.

@kgryte kgryte added the Obsolete Issue or pull request which is no longer relevant. label Jun 28, 2024
@hfhchan-plb
Copy link
Author

You're right. @segment/tsub was pulling in old versions of this library.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Obsolete Issue or pull request which is no longer relevant.
Projects
None yet
Development

No branches or pull requests

3 participants