-
-
Notifications
You must be signed in to change notification settings - Fork 115
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
Changed export from default to named #701
Comments
Hi @pawel-id ! Thanks for raising this issue and thanks for contributing in making this project better! Yep you're right, it is a breaking change in a minor version without communication. Here are how we suggest to deal with that:
|
It happens. I would treat it as a bug and restore previous behavior, then release v5.26.1. From semantic versioning point of view this is proper way to fix. |
Option 2 it is ! |
Shipped in release $ sfdx plugins:install sfdx-git-delta@latest-rc
$ sfdx plugins:install [email protected] Happy incremental deployment! |
It seems typescript clause
or
|
Shipped in release $ sfdx plugins:install sfdx-git-delta@latest-rc
$ sfdx plugins:install [email protected] Happy incremental deployment! |
We are using this tool as an imported module in our deployment tool. It works perfectly. Unfortunately we noticed that along with the latest v5.26.0 some breaking change has been introduced. Previously (i.e. v5.25.2 and older) the main function was exported as a default export. Then in order to consume the following code was required:
That way is still in readme, however the behaviour has changed to named export, and now it requires:
It would be great to follow semantic versioning rules and not to introduce breaking changes with minor changes. In other words please keep default export when doing minor version bumps.
The text was updated successfully, but these errors were encountered: