Skip to content
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

why is v3 a breaking change? #809

Open
jpw opened this issue Jan 17, 2022 · 2 comments
Open

why is v3 a breaking change? #809

jpw opened this issue Jan 17, 2022 · 2 comments

Comments

@jpw
Copy link

jpw commented Jan 17, 2022

Hi, thanks for releasing a new version.

Why is v3 a breaking change please? It's not clear to me from the changelog, and there is no migration guide. This would help us upgrade our apps. Thanks!

@sumeetkakkar
Copy link
Collaborator

43c0831 seems like a breaking change.

@jpw
Copy link
Author

jpw commented Jan 18, 2022

Thanks for your reply @sumeetkakkar !

Because I don't know how Dustjs works internally, I can't judge whether that is a breaking change or not. More importantly I cannot see what changes I might need to make in our apps to prevent them breaking when upgrading to v3. And that is what anyone upgrading would need to know. I hope that makes sense 🙂

Also I note that in this code comparison: v2.7.5...v3.0.1
...it looks like node 12 is the currently minimum supported version (which makes sense), I assume due to dependency updates? which would also be a breaking change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants