You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 ..........
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: