-
Notifications
You must be signed in to change notification settings - Fork 404
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 extensionPack
instead of extensionDependencies
property for defining pack
#562
Comments
@sandy081 - Is the new
We are asking because our current dependency is on version 1.23 for API functionality and we want to determine if we need to bump everything up to 1.26 to take advantage of this new |
@vazexqi Good question, yes you have to set your engine > 1.26.0 |
From release v1.26, defining an Extension Pack now uses a new property called
extensionPack
instead ofextensionDependencies
in package.json. This is because extensionDependencies is mainly used to define functional dependencies and an Extension Pack should not have any functional dependencies with its bundled extensions and they should be manageable independent of the pack.So please use
extensionPack
property for defining the pack.For more details refer to Release notes
The text was updated successfully, but these errors were encountered: