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
read up on what nodejs has to say about Peer Dependencies: https://nodejs.org/en/blog/npm/peer-dependencies to understand what version definition could make sense and why this is interesting in the first place.
The best way to determine what your peer dependency requirements should be is to actually follow semver. Assume that only changes in the host package's major version will break your plugin. Thus, if you've worked with every 1.x version of the host package, use "~1.0" or "1.x" to express this. If you depend on features introduced in 1.5.2, use ">= 1.5.2 < 2".
... also, it will show up in the "used by" section afterwards ;-)
The text was updated successfully, but these errors were encountered:
similar to what we've done in the copado repo (https://github.com/Accenture/sfmc-devtools-copado/blob/c0eb700def58c010d68787ad150fa3d4494b7305/package.json#LL12C10-L12C15) I would want you to add a definition of which mcdev version your extension requires in the form of a peer dependency in your package.json
read up on what nodejs has to say about Peer Dependencies: https://nodejs.org/en/blog/npm/peer-dependencies to understand what version definition could make sense and why this is interesting in the first place.
... also, it will show up in the "used by" section afterwards ;-)
The text was updated successfully, but these errors were encountered: