We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In all the @stdlib/assert-is-* packages, @stdlib/cli-ctor and @stdlib-fs-read-file are listed as dependencies, when they should be devDependencies.
@stdlib/assert-is-*
@stdlib/cli-ctor
@stdlib-fs-read-file
devDependencies
This causes huge deps trees when importing something simple like @stdlib/math-base-special-ldexp.
@stdlib/math-base-special-ldexp
No response
N/A
The text was updated successfully, but these errors were encountered:
👋 Hi there! 👋
And thank you for opening your first issue! We will get back to you shortly. 🏃 💨
Sorry, something went wrong.
@stdlib
@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.
stdlib
@stdlib/assert-is-boolean
v0.0.8
v0.2.1
@stdlib/assert-has-tostringtag-support
You're right. @segment/tsub was pulling in old versions of this library.
@segment/tsub
No branches or pull requests
Description
In all the
@stdlib/assert-is-*
packages,@stdlib/cli-ctor
and@stdlib-fs-read-file
are listed as dependencies, when they should bedevDependencies
.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
The text was updated successfully, but these errors were encountered: