This repository has been archived by the owner on Jul 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 198
Peer dependency issue with [email protected] #373
Milestone
Comments
I think this must be moved to dependencies. Because when using npm 3 with legacy bundling this throw error with module not found |
Any news? |
#371 relaxed the peer dependency to be 1.6.0 or greater. It doesn't look like it's made it into a release yet. |
Yes this is fixed a while ago. I can put it on the release branch over the
weekend.
…On Jun 3, 2017 11:15, "reduckted" ***@***.***> wrote:
#371 <#371>
relaxed the peer dependency to be 1.6.0 or greater. It doesn't look like
it's made it into a release yet.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#373 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AALYIWfHc8CSg7O9waQp5giTtcnCySYDks5sASQ0gaJpZM4Nd8z2>
.
|
Sounds good - do you know when that will be released? |
Closing this as a duplicate of #371 and triggering the release today. |
4 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Run into the warning below in relation to peer dependency mismatch
warning "[email protected]" has incorrect peer dependency "[email protected]".
Might be worth upgrading tsutils to the latest version if possible.
The text was updated successfully, but these errors were encountered: