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
Thanks for the heads up. This is what my plan is going forward.
keep html2jade as-is for users still using jade as-is.
consider creating html2pug module for pug users.
FYI, I am not a big fan of semver and, to me, breaking backward-compatibility should result in name change like foo2 instead of just keeping same name and bumping major version number.
In order to keep the modules that rely on html2jade from breaking, sticking with .jade, as-is, is the better approach. I will soon start working on a new major release of this module and an option might be to simply provide a flag, something along the lines of --pug (for CLI) and an option for programmatic use, to provide support for the new features.
https://pugjs.org/api/migration-v2.html#project-rename
The text was updated successfully, but these errors were encountered: