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

Use of tag 1.0.1 causes report of an undeclared dependency on has-symbols #3

Closed
Peter-Sparksuite opened this issue Feb 1, 2024 · 3 comments

Comments

@Peter-Sparksuite
Copy link

With the recent release of 1.0.1, a project that has been using 1.0.0 is now failing, with error messages indicating there is an undeclared dependency that's been introduced.

We'd really like to not have the dependency on has-symbols at all, if possible.

Can this be fixed please?

Error: has-tostringtag tried to access has-symbols, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
Required package: has-symbols (via "has-symbols/shams")
Required by: has-tostringtag@npm:1.0.1 ..........
@ljharb ljharb closed this as completed in 300520c Feb 1, 2024
@ljharb
Copy link
Member

ljharb commented Feb 1, 2024

Yes, my mistake, thanks - 999e009 caused the problem.

@ljharb
Copy link
Member

ljharb commented Feb 1, 2024

Released in v1.0.2.

@Peter-Sparksuite
Copy link
Author

Confirmed: That took care of it.

Thank you much! :)

somnisomni added a commit to somnisomni/MyBoothManager that referenced this issue Feb 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants